<?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-29T04:43:52.567054+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-64291</id>
    <title>CVE-2026-64291 — iommufd: Set veventq_depth upper bound</title>
    <updated>2026-09-29T04:43:52.569076+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>iommufd: Set veventq_depth upper bound</p>
<p>iommufd_veventq_alloc() accepts any !0 veventq_depth from userspace, with
an upper bound at U32_MAX.</p>
<p>This leaves a vulnerability where userspace can allocate excessively large
queues to exhaust kernel memory reserves.</p>
<p>Cap the veventq_depth (maximum number of entries) to 1 &lt;&lt; 19, matching the
maximum number of entries in the SMMUv3 EVTQ (the largest use case today).</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-64291"/>
  </entry>
</feed>
