<?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>Fri, 02 Oct 2026 05:37:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80613 — veth: fix NAPI leak in XDP enable error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80613</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;veth: fix NAPI leak in XDP enable error path&lt;/p&gt;
&lt;p&gt;During XDP enablement in veth, if xdp_rxq_info_reg() or
xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.&lt;/p&gt;
&lt;p&gt;However, the rollback loop:
	for (i--; i &amp;gt;= start; i--) {&lt;/p&gt;
&lt;p&gt;decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This
correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as
registration failed or was already cleaned up), but it also
erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.&lt;/p&gt;
&lt;p&gt;Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves
a dangling napi_struct in the device&amp;#39;s napi_list. When the veth
device is later destroyed, the freed queue memory (which contains the
leaked NAPI structure) can be reused.&lt;/p&gt;
&lt;p&gt;The subsequent device teardown iterates the NAPI list and
corrupts the reallocated memory, leading to UAF.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly deleting the NAPI association for the failed
index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&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;veth: fix NAPI leak in XDP enable error path&lt;/p&gt;
&lt;p&gt;During XDP enablement in veth, if xdp_rxq_info_reg() or
xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.&lt;/p&gt;
&lt;p&gt;However, the rollback loop:
	for (i--; i &amp;gt;= start; i--) {&lt;/p&gt;
&lt;p&gt;decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This
correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as
registration failed or was already cleaned up), but it also
erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.&lt;/p&gt;
&lt;p&gt;Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves
a dangling napi_struct in the device&amp;#39;s napi_list. When the veth
device is later destroyed, the freed queue memory (which contains the
leaked NAPI structure) can be reused.&lt;/p&gt;
&lt;p&gt;The subsequent device teardown iterates the NAPI list and
corrupts the reallocated memory, leading to UAF.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly deleting the NAPI association for the failed
index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80613</guid>
    </item>
  </channel>
</rss>
