<?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>Thu, 01 Oct 2026 20:57:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53211 — net/l2tp: fix warning in l2tp_exit_net found by syzbot</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-53211</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;net/l2tp: fix warning in l2tp_exit_net found by syzbot&lt;/p&gt;
&lt;p&gt;In l2tp&amp;#39;s net exit handler, we check that an IDR is empty before
destroying it:&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(!idr_is_empty(&amp;amp;pn-&amp;gt;l2tp_tunnel_idr));
	idr_destroy(&amp;amp;pn-&amp;gt;l2tp_tunnel_idr);&lt;/p&gt;
&lt;p&gt;By forcing memory allocation failures in idr_alloc_32, syzbot is able
to provoke a condition where idr_is_empty returns false despite there
being no items in the IDR. This turns out to be because the radix tree
of the IDR contains only internal radix-tree nodes and it is this that
causes idr_is_empty to return false. The internal nodes are cleaned by
idr_destroy.&lt;/p&gt;
&lt;p&gt;Use idr_for_each to check that the IDR is empty instead of
idr_is_empty to avoid the problem.&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;net/l2tp: fix warning in l2tp_exit_net found by syzbot&lt;/p&gt;
&lt;p&gt;In l2tp&amp;#39;s net exit handler, we check that an IDR is empty before
destroying it:&lt;/p&gt;
&lt;p&gt;WARN_ON_ONCE(!idr_is_empty(&amp;amp;pn-&amp;gt;l2tp_tunnel_idr));
	idr_destroy(&amp;amp;pn-&amp;gt;l2tp_tunnel_idr);&lt;/p&gt;
&lt;p&gt;By forcing memory allocation failures in idr_alloc_32, syzbot is able
to provoke a condition where idr_is_empty returns false despite there
being no items in the IDR. This turns out to be because the radix tree
of the IDR contains only internal radix-tree nodes and it is this that
causes idr_is_empty to return false. The internal nodes are cleaned by
idr_destroy.&lt;/p&gt;
&lt;p&gt;Use idr_for_each to check that the IDR is empty instead of
idr_is_empty to avoid the problem.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-53211</guid>
    </item>
  </channel>
</rss>
