<?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 06:29:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23326 — xsk: Fix fragment node deletion to prevent buffer leak</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23326</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;xsk: Fix fragment node deletion to prevent buffer leak&lt;/p&gt;
&lt;p&gt;After commit b692bf9a7543 (&amp;#34;xsk: Get rid of xdp_buff_xsk::xskb_list_node&amp;#34;),
the list_node field is reused for both the xskb pool list and the buffer
free list, this causes a buffer leak as described below.&lt;/p&gt;
&lt;p&gt;xp_free() checks if a buffer is already on the free list using
list_empty(&amp;amp;xskb-&amp;gt;list_node). When list_del() is used to remove a node
from the xskb pool list, it doesn&amp;#39;t reinitialize the node pointers.
This means list_empty() will return false even after the node has been
removed, causing xp_free() to incorrectly skip adding the buffer to the
free list.&lt;/p&gt;
&lt;p&gt;Fix this by using list_del_init() instead of list_del() in all fragment
handling paths, this ensures the list node is reinitialized after removal,
allowing the list_empty() to work correctly.&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;xsk: Fix fragment node deletion to prevent buffer leak&lt;/p&gt;
&lt;p&gt;After commit b692bf9a7543 (&amp;#34;xsk: Get rid of xdp_buff_xsk::xskb_list_node&amp;#34;),
the list_node field is reused for both the xskb pool list and the buffer
free list, this causes a buffer leak as described below.&lt;/p&gt;
&lt;p&gt;xp_free() checks if a buffer is already on the free list using
list_empty(&amp;amp;xskb-&amp;gt;list_node). When list_del() is used to remove a node
from the xskb pool list, it doesn&amp;#39;t reinitialize the node pointers.
This means list_empty() will return false even after the node has been
removed, causing xp_free() to incorrectly skip adding the buffer to the
free list.&lt;/p&gt;
&lt;p&gt;Fix this by using list_del_init() instead of list_del() in all fragment
handling paths, this ensures the list node is reinitialized after removal,
allowing the list_empty() to work correctly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23326</guid>
    </item>
  </channel>
</rss>
