Android · Kernel · CWE-416 · published 2024-06-10
CVE-2024-36971Android Kernel Remote Code Execution Vulnerability
This week Known exploited in the wild.
CVE-2024-36971 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2024-08-07. EPSS estimates a 2.7% chance of exploitation in the next 30 days, higher than 86% of all CVEs. This Kernel vulnerability: CVSS 7.8 (v3.1), a successful attack gives total control of the component. Patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux. US federal agencies must remediate by 2024-08-28. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (federal due date 2024-08-28)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | linux | Fixed in 6.9.7-1 |
| 12 bookworm | linux | Fixed in 6.1.94-1 | |
| Ubuntu (+134 more packages) | 24.04 LTS | linux | Fixed in 6.8.0-44.44 |
| 22.04 LTS | linux | Fixed in 5.15.0-121.131 | |
| 20.04 LTS | linux | Fixed in 5.4.0-192.212 | |
| Red Hat Enterprise Linux | RHEL 9 | kernel | Fixed in 5.14.0-427.31.1.el9_4 RHSA-2024:5363 |
| RHEL 8 | kernel | Fixed in 4.18.0-553.16.1.el8_10 RHSA-2024:5101 | |
| RHEL 8 | kernel-rt | Fixed in 4.18.0-553.16.1.rt7.357.el8_10 RHSA-2024:5102 | |
| RHEL 7 | kernel-rt | Won’t fix | |
| RHEL 6 | kernel | Not affected |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Mobile & device firmwareAndroid Kernel
Remote Code ExecutionCVE-2024-36971
Why: Known exploited in the wild.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2024-08-07 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 2.7% (86th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.8 (v3.1)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-416: Use After Free
More from this vendor: all Android vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Linux Linux
a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to before051c0bde9f0450a2ec3d62a86d2a0d2fad117f13(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to beforedb0082825037794c5dba9959c9de13ca34cc5e72(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to before2295a7ef5c8c49241bff769e7826ef2582e532a6(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to beforeeacb8b195579c174a6d3e12a9690b206eb7f28cf(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to before81dd3c82a456b0015461754be7cb2693991421b4(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to before5af198c387128a9d2ddd620b0f0803564a4d4508(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to beforeb8af8e6118a6605f0e495a58d591ca94a85a50fc(affected)a87cb3e48ee86d29868d3f59cfb9ce1a8fa63314to before92f1655aa2b2294d0b49925f3b875a634bd3b59e(affected)
- Linux Linux
4.6(affected)0to before4.6(unaffected)4.19.316through4.19.*(unaffected)5.4.278through5.4.*(unaffected)5.10.219through5.10.*(unaffected)5.15.161through5.15.*(unaffected)6.1.94through6.1.*(unaffected)6.6.34through6.6.*(unaffected)6.9.4through6.9.*(unaffected)6.10through*(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.