<?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 16:32:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36971 — net: fix __dst_negative_advice() race</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36971</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix __dst_negative_advice() race&lt;/p&gt;
&lt;p&gt;__dst_negative_advice() does not enforce proper RCU rules when
sk-&amp;gt;dst_cache must be cleared, leading to possible UAF.&lt;/p&gt;
&lt;p&gt;RCU rules are that we must first clear sk-&amp;gt;sk_dst_cache,
then call dst_release(old_dst).&lt;/p&gt;
&lt;p&gt;Note that sk_dst_reset(sk) is implementing this protocol correctly,
while __dst_negative_advice() uses the wrong order.&lt;/p&gt;
&lt;p&gt;Given that ip6_negative_advice() has special logic
against RTF_CACHE, this means each of the three -&amp;gt;negative_advice()
existing methods must perform the sk_dst_reset() themselves.&lt;/p&gt;
&lt;p&gt;Note the check against NULL dst is centralized in
__dst_negative_advice(), there is no need to duplicate
it in various callbacks.&lt;/p&gt;
&lt;p&gt;Many thanks to Clement Lecigne for tracking this issue.&lt;/p&gt;
&lt;p&gt;This old bug became visible after the blamed commit, using UDP sockets.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: fix __dst_negative_advice() race&lt;/p&gt;
&lt;p&gt;__dst_negative_advice() does not enforce proper RCU rules when
sk-&amp;gt;dst_cache must be cleared, leading to possible UAF.&lt;/p&gt;
&lt;p&gt;RCU rules are that we must first clear sk-&amp;gt;sk_dst_cache,
then call dst_release(old_dst).&lt;/p&gt;
&lt;p&gt;Note that sk_dst_reset(sk) is implementing this protocol correctly,
while __dst_negative_advice() uses the wrong order.&lt;/p&gt;
&lt;p&gt;Given that ip6_negative_advice() has special logic
against RTF_CACHE, this means each of the three -&amp;gt;negative_advice()
existing methods must perform the sk_dst_reset() themselves.&lt;/p&gt;
&lt;p&gt;Note the check against NULL dst is centralized in
__dst_negative_advice(), there is no need to duplicate
it in various callbacks.&lt;/p&gt;
&lt;p&gt;Many thanks to Clement Lecigne for tracking this issue.&lt;/p&gt;
&lt;p&gt;This old bug became visible after the blamed commit, using UDP sockets.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36971</guid>
    </item>
  </channel>
</rss>
