CVE-2024-36971
Android — Android Kernel Remote Code Execution Vulnerability
Android · CWE-416 — Use after free · in CISA KEV since 2024-08-07
EVRS 75 of 100 Urgent
Patch This Cycle
Rank 1,202 of 2,960 tracked
Raised to the floor for a confirmed exploited vulnerability.
Why it scores 75
Evidence available: 6 of 7 signalsListed in the CISA KEV catalog, and an EPSS probability of 0.027.
- CISA KEVApplied
- RansomwareDid not apply
- Vendor exploitationDid not apply
- EPSSApplied
- Microsoft Exploitability IndexNot applicable
- Pre-patch disclosureNo data
- KEV recencyDid not apply
- CVSSApplied
The band answers “how soon”, not “how bad”. No data for: Pre-patch disclosure. Why some signals show no data
Fix
Patch or fixed version identifiedCISA required action
- 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
- nvd.nist.gov/…/CVE-2024-36971
Fixed in
linux-azure -> 4.15.0-1182.197~14.04.1 | linux -> 6.1.94-1 | linux -> 6.9.7-1
Affected versions
- debian linux
10.0 - linux kernel
>= 4.6 < 4.19.316>= 4.20 < 5.4.278>= 5.5 < 5.10.219>= 5.11 < 5.15.161>= 5.16 < 6.1.94>= 6.2 < 6.6.34>= 6.7 < 6.9.4
Remediation
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Fixed versions from NVD.
Evidence
Each value with its source| Measure | Value | Source |
|---|---|---|
| CVSS base scoreHow severe the flaw is in itself. It does not say how likely an attack is. | 7.8 | NVD |
| FIRST EPSSFIRST's estimate of the chance this is exploited in the next 30 days, and how that ranks against all CVEs. | 0.027 (85.8th pctl) | FIRST EPSS |
| Actively exploitedWhether a source of record has confirmed attacks using it in the wild. | Confirmed | CISA KEV |
| Ransomware campaign useWhether CISA has seen ransomware operators use it. | Unknown or none | CISA KEV |
| CISA remediation deadlineThe date US federal agencies must have fixed or mitigated it. | 2024-08-28 · KEV since 2024 · listed over a year | CISA KEV |
| Public exploit moduleA module existing is not the same as active exploitation. | None known | Metasploit |
| EUVD cross-referenceENISA's record: CVSS 7.8 (v3.1), assigned by Linux. | Listed | ENISA EUVD |
Description
NVDIn 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.
What CISA says to do