<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T13:03:25.954832+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-74306</id>
    <title>CVE-2026-74306 — vfio/qat: fix f_pos race in qat_vf_resume_write()</title>
    <updated>2026-09-29T13:03:27.035087+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>vfio/qat: fix f_pos race in qat_vf_resume_write()</p>
<p>qat_vf_resume_write() checks filp-&gt;f_pos before taking migf-&gt;lock, but
copies into the migration-state buffer after taking the lock and
re-reading the shared file position.</p>
<p>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.</p>
<p>Take migf-&gt;lock before doing the boundary checks.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74306"/>
  </entry>
</feed>
