Android Kernel Remote Code Execution Vulnerability
Linux — Linux
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.
7.8
2.7%
Vector breakdown
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- Jun 10, 2024
- Modified
- Jun 17, 2026
- Added to KEV
- Aug 7, 2024
- Federal patch due
- Aug 28, 2024
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
1 foundWeaponization
Public repositories whose name or description references CVE-2024-36971, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
References
Frequently asked questions
What is CVE-2024-36971?
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.
How severe is CVE-2024-36971?
CVE-2024-36971 has a CVSS base score of 7.8 out of 10 (CVSS 3.1).
Is CVE-2024-36971 actively exploited in the wild?
Yes. CVE-2024-36971 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Aug 7, 2024, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2024-36971?
2.7% - meaning FIRST.org's EPSS model estimates a 2.7% probability this vulnerability will be exploited in the wild within 30 days (85% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2024-36971?
We found 1 public GitHub repository referencing CVE-2024-36971, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2024-36971?
CVE-2024-36971 is classified under CWE-416 (CWE-416 Use After Free).
Cross-checked against
Impactr finds and proves whether CVE-2024-36971 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist