CVE-2024-36971: Android Kernel Remote Code Execution Vulnerability
- Is it exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on , 58 days after the CVE record was published.
- How likely is exploitation in the next 30 days?
- 2.7%
EPSS score, percentile 85.9 of all scored records
- How severe?
- 7.8 High
CVSS v3.1 base score, given by the CNA
- What should I do?
CISA deadline . Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
The CVE record links no vendor advisory, patch or mitigation.
- Which versions are affected?
Affected
- 4.6
Unaffected before 4.6; 4.19.316; 5.4.278; 5.10.219; 5.15.161; 6.1.94; and 3 more
Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of ; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of ; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of . About the data.
What to do
Required action, set by CISA
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA due date for this action: .
Advisories and patches
The CVE record links no vendor advisory, patch or mitigation.
Linked from CISA's catalog entry
- https://source.android.com/docs/security/bulletin/2024-08-01
- https://lore.kernel.org/linux-cve-announce/[email protected]/T/#u
- https://nvd.nist.gov/vuln/detail/CVE-2024-36971
Affected products and versions
As listed in the CVE record.
| Status | Versions |
|---|---|
| Affected | from a87cb3e48ee8 to before 051c0bde9f04 |
| Affected | from a87cb3e48ee8 to before db0082825037 |
| Affected | from a87cb3e48ee8 to before 2295a7ef5c8c |
| Affected | from a87cb3e48ee8 to before eacb8b195579 |
| Affected | from a87cb3e48ee8 to before 81dd3c82a456 |
| Affected | from a87cb3e48ee8 to before 5af198c38712 |
| Affected | from a87cb3e48ee8 to before b8af8e6118a6 |
| Affected | from a87cb3e48ee8 to before 92f1655aa2b2 |
Versions not listed are: unaffected.
| Status | Versions |
|---|---|
| Affected | 4.6 |
| Unaffected | before 4.6 |
| Unaffected | 4.19.316 |
| Unaffected | 5.4.278 |
| Unaffected | 5.10.219 |
| Unaffected | 5.15.161 |
| Unaffected | 6.1.94 |
| Unaffected | 6.6.34 |
| Unaffected | 6.9.4 |
| Unaffected | 6.10 |
Versions not listed are: affected.
Versions the record lists as unaffected: 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.94, 6.6.34, 6.9.4, 6.10.
Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of . About the data.
About this vulnerability
Android contains an unspecified vulnerability in the kernel that allows for remote code execution. This vulnerability resides in Linux Kernel and could impact other products, including but not limited to Android OS.
Summary: CISA's KEV catalog, as of .
- CISA added CVE-2024-36971 to its Known Exploited Vulnerabilities (KEV) catalog on 7 Aug 2024.
- CISA's ransomware flag for this entry is "Unknown": no evidence of ransomware use in the catalog, which is not proof of none.
- The due date CISA sets for the required action is 28 Aug 2024.
- The CVE record was published on 10 Jun 2024, 58 days before it was added to KEV.
- The CVE record carries a CVSS v3.1 base score of 7.8 (High), given by its CNA.
- FIRST's EPSS model puts the probability of exploitation in the next 30 days at 2.7% (percentile 85.9), as of 28 Oct 2026.
- CISA's SSVC assessment in the CVE record: exploitation active, automatable no, technical impact total.
Source: CISA Known Exploited Vulnerabilities (KEV) catalog, 2026.10.28, as of ; CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of ; FIRST Exploit Prediction Scoring System (EPSS), v2026.06.15, as of . About the data.
Description
net: fix __dst_negative_advice() race
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.
Source: CVE List V5 (CVE Program), cve_2026-10-28_0000Z, as of . About the data.
Weakness
- CWE-416: Use After Free
CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record and the KEV entry.
Timeline
| Date | Event |
|---|---|
| CVE record published | |
| Added to CISA KEV | |
| CISA due date for the required action | |
| CVE record last updated |
References
- git.kernel.org
- git.kernel.org
- git.kernel.org
- git.kernel.org
- git.kernel.org
- git.kernel.org
- git.kernel.org
- git.kernel.org
More exploited Android vulnerabilities
- CVE-2025-48595: Android Framework Integer Overflow Vulnerability
- CVE-2025-48572: Android Framework Privilege Escalation Vulnerability
- CVE-2025-48633: Android Framework Information Disclosure Vulnerability
- CVE-2025-48543: Android Runtime Use-After-Free Vulnerability
- CVE-2024-43093: Android Framework Privilege Escalation Vulnerability
- CVE-2024-32896: Android Pixel Privilege Escalation Vulnerability