<?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>Mon, 05 Oct 2026 22:38:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50036 — net: do not delay dst_entries_add() in dst_release()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50036</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: do not delay dst_entries_add() in dst_release()&lt;/p&gt;
&lt;p&gt;dst_entries_add() uses per-cpu data that might be freed at netns
dismantle from ip6_route_net_exit() calling dst_entries_destroy()&lt;/p&gt;
&lt;p&gt;Before ip6_route_net_exit() can be called, we release all
the dsts associated with this netns, via calls to dst_release(),
which waits an rcu grace period before calling dst_destroy()&lt;/p&gt;
&lt;p&gt;dst_entries_add() use in dst_destroy() is racy, because
dst_entries_destroy() could have been called already.&lt;/p&gt;
&lt;p&gt;Decrementing the number of dsts must happen sooner.&lt;/p&gt;
&lt;p&gt;Notes:&lt;/p&gt;
&lt;p&gt;1) in CONFIG_XFRM case, dst_destroy() can call
   dst_release_immediate(child), this might also cause UAF
   if the child does not have DST_NOCOUNT set.
   IPSEC maintainers might take a look and see how to address this.&lt;/p&gt;
&lt;p&gt;2) There is also discussion about removing this count of dst,
   which might happen in future kernels.&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: do not delay dst_entries_add() in dst_release()&lt;/p&gt;
&lt;p&gt;dst_entries_add() uses per-cpu data that might be freed at netns
dismantle from ip6_route_net_exit() calling dst_entries_destroy()&lt;/p&gt;
&lt;p&gt;Before ip6_route_net_exit() can be called, we release all
the dsts associated with this netns, via calls to dst_release(),
which waits an rcu grace period before calling dst_destroy()&lt;/p&gt;
&lt;p&gt;dst_entries_add() use in dst_destroy() is racy, because
dst_entries_destroy() could have been called already.&lt;/p&gt;
&lt;p&gt;Decrementing the number of dsts must happen sooner.&lt;/p&gt;
&lt;p&gt;Notes:&lt;/p&gt;
&lt;p&gt;1) in CONFIG_XFRM case, dst_destroy() can call
   dst_release_immediate(child), this might also cause UAF
   if the child does not have DST_NOCOUNT set.
   IPSEC maintainers might take a look and see how to address this.&lt;/p&gt;
&lt;p&gt;2) There is also discussion about removing this count of dst,
   which might happen in future kernels.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50036</guid>
    </item>
  </channel>
</rss>
