<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 11:29:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74306 — vfio/qat: fix f_pos race in qat_vf_resume_write()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74306</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2026-74306</guid>
    </item>
  </channel>
</rss>
