<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 08:41:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74306</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74306</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74306</guid>
    </item>
    <item>
      <title>EUVD-2026-354161</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354161</link>
      <description>EUVD-2026-354161</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354161</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74306</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74306</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/qat: fix f_pos race in qat_vf_resume_write()&lt;/p&gt;
&lt;p&gt;qat_vf_resume_write() checks filp-&amp;gt;f_pos before taking migf-&amp;gt;lock, but
copies into the migration-state buffer after taking the lock and
re-reading the shared file position.&lt;/p&gt;
&lt;p&gt;Two concurrent writers could therefore pass the bounds check with the
old offset, then have the second writer copy after the first advanced
f_pos, writing past the end of the migration-state buffer.&lt;/p&gt;
&lt;p&gt;Take migf-&amp;gt;lock before doing the boundary checks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/qat: fix f_pos race in qat_vf_resume_write()&lt;/p&gt;
&lt;p&gt;qat_vf_resume_write() checks filp-&amp;gt;f_pos before taking migf-&amp;gt;lock, but
copies into the migration-state buffer after taking the lock and
re-reading the shared file position.&lt;/p&gt;
&lt;p&gt;Two concurrent writers could therefore pass the bounds check with the
old offset, then have the second writer copy after the first advanced
f_pos, writing past the end of the migration-state buffer.&lt;/p&gt;
&lt;p&gt;Take migf-&amp;gt;lock before doing the boundary checks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74306</guid>
    </item>
    <item>
      <title>GHSA-5q42-qm7h-h2q2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5q42-qm7h-h2q2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/qat: fix f_pos race in qat_vf_resume_write()&lt;/p&gt;
&lt;p&gt;qat_vf_resume_write() checks filp-&amp;gt;f_pos before taking migf-&amp;gt;lock, but
copies into the migration-state buffer after taking the lock and
re-reading the shared file position.&lt;/p&gt;
&lt;p&gt;Two concurrent writers could therefore pass the bounds check with the
old offset, then have the second writer copy after the first advanced
f_pos, writing past the end of the migration-state buffer.&lt;/p&gt;
&lt;p&gt;Take migf-&amp;gt;lock before doing the boundary checks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/qat: fix f_pos race in qat_vf_resume_write()&lt;/p&gt;
&lt;p&gt;qat_vf_resume_write() checks filp-&amp;gt;f_pos before taking migf-&amp;gt;lock, but
copies into the migration-state buffer after taking the lock and
re-reading the shared file position.&lt;/p&gt;
&lt;p&gt;Two concurrent writers could therefore pass the bounds check with the
old offset, then have the second writer copy after the first advanced
f_pos, writing past the end of the migration-state buffer.&lt;/p&gt;
&lt;p&gt;Take migf-&amp;gt;lock before doing the boundary checks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5q42-qm7h-h2q2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74306</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74306</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/qat: fix f_pos race in qat_vf_resume_write() qat_vf_resume_write() checks filp-&amp;gt;f_pos before taking migf-&amp;gt;lock, but copies into the migration-state buffer after taking the lock and re-reading the shared file position. Two concurrent writers could therefore pass the bounds check with the old offset, then have the second writer copy after the first advanced f_pos, writing past the end of the migration-state buffer. Take migf-&amp;gt;lock before doing the boundary checks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/qat: fix f_pos race in qat_vf_resume_write() qat_vf_resume_write() checks filp-&amp;gt;f_pos before taking migf-&amp;gt;lock, but copies into the migration-state buffer after taking the lock and re-reading the shared file position. Two concurrent writers could therefore pass the bounds check with the old offset, then have the second writer copy after the first advanced f_pos, writing past the end of the migration-state buffer. Take migf-&amp;gt;lock before doing the boundary checks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74306</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
