In the Linux kernel, the following vulnerability has been resolved:
net: fix __dst_negative_advice() race
__dst_negative_advice() does not enforce proper RCU rules when
sk->dst_cache must be cleared, leading to possible UAF.
RCU rules are that we must first clear sk->sk_dst_cache,
then call dst_release(old_dst).
Note that sk_dst_reset(sk) is implementing this protocol correctly,
while __dst_negative_advice() uses the wrong order.
Given that ip6_negative_advice() has special logic
against RTF_CACHE, this means each of the three ->negative_advice()
existing methods must perform the sk_dst_reset() themselves.
Note the check against NULL dst is centralized in
__dst_negative_advice(), there is no need to duplicate
it in various callbacks.
Many thanks to Clement Lecigne for tracking this issue.
This old bug became visible after the blamed commit, using UDP sockets.
Security readout for executives and security teams
Plain-English summary
A Linux kernel networking race can leave the kernel using freed memory. A locally authenticated, low-privileged attacker may potentially compromise confidentiality, integrity, and availability. CISA lists CVE-2024-36971 as known exploited, making remediation urgent despite the source bundle providing no details about observed attacks.
Executive priority
Treat as a high-priority kernel update because exploitation is known and successful abuse could affect the entire host. Accelerate remediation on systems permitting local users, containers, or other untrusted workloads. Use vendor-specific build guidance because the supplied affected-version listing is ambiguous.
Technical view
__dst_negative_advice() released a cached network destination before clearing sk_dst_cache, violating required RCU ordering and enabling a use-after-free. The issue became observable with UDP sockets. The supplied CVSS 3.1 score is 7.8 with local, low-complexity, low-privilege exploitation and no user interaction.
Likely exposure
Exposure is most likely on Linux systems running kernel builds that lack the stable correction, particularly where untrusted or lower-privileged users can execute local workloads. The supplied version data is not sufficiently clear for reliable range-based determination; assess vendor kernel builds and backports individually.
Exploitation context
CISA KEV status supports active exploitation in the wild. However, the supplied sources do not describe exploitation scale, targeted sectors, attack chains, or whether public exploit code exists. The CVSS vector indicates an attacker first requires low-privileged local access.
Researcher notes
CWE-416 applies. The corrective design clears sk_dst_cache before releasing old_dst, consistent with sk_dst_reset(). Each negative_advice callback must perform the reset because IPv6 has RTF_CACHE-specific handling. The bundle supplies multiple stable commits but does not map each commit clearly to every affected kernel build.
Mitigation direction
Upgrade to a vendor-supported kernel containing the CVE-2024-36971 correction or an equivalent backport.
Consult the Linux distribution or appliance vendor for exact fixed build identifiers.
Prioritize shared, multi-user, and externally reachable workload hosts where local code execution is possible.
Restrict unnecessary local accounts and untrusted workload execution until patching is complete.
Reboot into the corrected kernel and remove vulnerable kernels from normal boot options.
Validation and detection
Record each system's running kernel release, build, distribution, and architecture.
Compare builds against vendor advisories and documented backports, not upstream version numbers alone.
Confirm the running kernel contains the applicable stable fix or vendor-equivalent change.
Verify systems rebooted successfully into the corrected kernel after installation.
Review kernel crash and networking telemetry for unexplained use-after-free or UDP-related instability.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.