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…
Browse: All 2024 CVEs · All vendors
- CVSS score
- 7.8 High
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- CISA KEV
- Yes — actively exploited (added 2024-08-07, remediation due 2024-08-28)
- Weakness (CWE)
- CWE-416
- Published
- 2024-06-10
- Last modified
- 2026-06-17
- NVD status
- Analyzed
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.
Affected products
- debian debian linux
- linux linux kernel
Affected ranges per NVD CPE data; confirm exact versions in the vendor advisory.
Required action (CISA)
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Federal remediation deadline: 2024-08-28.
How to prioritize this
This vulnerability is on the CISA KEV list, meaning it is being actively exploited — treat it as urgent regardless of the raw CVSS number. Use the live CVE lookup for the latest NVD data, and the CVSS 3.1 calculator to model your own environmental score.
References
- https://git.kernel.org/stable/c/051c0bde9f0450a2ec3d62a86d2a0d2fad117f13
- https://git.kernel.org/stable/c/2295a7ef5c8c49241bff769e7826ef2582e532a6
- https://git.kernel.org/stable/c/5af198c387128a9d2ddd620b0f0803564a4d4508
- https://git.kernel.org/stable/c/81dd3c82a456b0015461754be7cb2693991421b4
- https://git.kernel.org/stable/c/92f1655aa2b2294d0b49925f3b875a634bd3b59e
- https://git.kernel.org/stable/c/b8af8e6118a6605f0e495a58d591ca94a85a50fc
- https://git.kernel.org/stable/c/db0082825037794c5dba9959c9de13ca34cc5e72
- https://git.kernel.org/stable/c/eacb8b195579c174a6d3e12a9690b206eb7f28cf
FAQ
Is CVE-2024-36971 actively exploited?
Yes. CISA added CVE-2024-36971 to its Known Exploited Vulnerabilities (KEV) catalog on 2024-08-07, with a federal remediation deadline of 2024-08-28. A KEV listing means real-world exploitation is confirmed, so patching this should be prioritized above many higher-CVSS bugs that aren't being exploited.
What is the CVSS score of CVE-2024-36971?
CVE-2024-36971 has a CVSS base score of 7.8 (High). Its vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Related vulnerabilities
- CVE-2021-1048 — Android Kernel
- CVE-2021-0920 — Android Kernel
- CVE-2025-48595 — Android Framework
- CVE-2025-48633 — Android Framework
- CVE-2025-48572 — Android Framework
- CVE-2025-48543 — Android Runtime
Data source: NVD & CISA KEV. Shown as-is; nothing added. Last generated from NVD data — re-check the live tool for updates.
weekly kev brief
Patch what's actually being exploited.
One email a week: the KEV additions that matter, prioritized — no noise.
Free. No spam. Unsubscribe anytime. Delivered by Beehiiv.