CVE-2024-36971
CVE-2024-36971 is a high-severity vulnerability (CVSS 3.1 base score 7.8). Android contains an unspecified vulnerability in the kernel that allows for remote code execution. CISA added it to the Known Exploited Vulnerabilities catalog on 2024-08-07, with a remediation due date of 2024-08-28 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 2.7% probability of exploitation in the next 30 days, in the 86th percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.8 HIGH
- EPSS
- 2.7% (86th pct)
- CISA KEV
- Exploited
- Published
- 2024-06-10
- Weakness
- CWE-416
Android Kernel Remote Code Execution Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: https://source.android.com/docs/security/bulletin/2024-08-01, https://lore.kernel.org/linux-cve-announce/20240610090330.1347021-2-lee@kernel.org/T/#u ; https://nvd.nist.gov/vuln/detail/CVE-2024-36971
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2024-36971 to the KEV catalog 58 days after its CVE record was published. The median for entries added in 2024 is 21.5 days.
- It is one of 17 Android entries in the CISA KEV catalog, and one of 6 added in 2024.
- Its current EPSS score (2.7%) is higher than that of 10% of CISA KEV entries.
Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2024-08-08).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| Linux | Linux Linux | a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <051c0bde9f0450a2ec3d62a86d2a0d2fad117f13 a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <db0082825037794c5dba9959c9de13ca34cc5e72 a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <2295a7ef5c8c49241bff769e7826ef2582e532a6 a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <eacb8b195579c174a6d3e12a9690b206eb7f28cf a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <81dd3c82a456b0015461754be7cb2693991421b4 a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <5af198c387128a9d2ddd620b0f0803564a4d4508 a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <b8af8e6118a6605f0e495a58d591ca94a85a50fc a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314 to <92f1655aa2b2294d0b49925f3b875a634bd3b59e |
| Linux | Linux Linux | 4.6 0 to <4.6 (unaffected) 4.19.316 to 4.19.* (unaffected) 5.4.278 to 5.4.* (unaffected) 5.10.219 to 5.10.* (unaffected) 5.15.161 to 5.15.* (unaffected) 6.1.94 to 6.1.* (unaffected) 6.6.34 to 6.6.* (unaffected) 6.9.4 to 6.9.* (unaffected) 6.10 to * (unaffected) |
References
9 linksOther references
- https://git.kernel.org/stable/c/051c0bde9f0450a2ec3d62a86d2a0d2fad117f13
- https://git.kernel.org/stable/c/db0082825037794c5dba9959c9de13ca34cc5e72
- https://git.kernel.org/stable/c/2295a7ef5c8c49241bff769e7826ef2582e532a6
- https://git.kernel.org/stable/c/eacb8b195579c174a6d3e12a9690b206eb7f28cf
- https://git.kernel.org/stable/c/81dd3c82a456b0015461754be7cb2693991421b4
- https://git.kernel.org/stable/c/5af198c387128a9d2ddd620b0f0803564a4d4508
- https://git.kernel.org/stable/c/b8af8e6118a6605f0e495a58d591ca94a85a50fc
- https://git.kernel.org/stable/c/92f1655aa2b2294d0b49925f3b875a634bd3b59e
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Record Details
- Published
- 2024-06-10
- Last updated
- 2026-08-05
- Assigner (CNA)
- Linux
- Credited to
- -
More from Android
Android Kernel Use-After-Free Vulnerability
Android Kernel Race Condition Vulnerability
Android Kernel Use-After-Free Vulnerability
Android OS Privilege Escalation Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.