CVE-2024-36971

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-08-07), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 3%CVSS: 7.8Exploit: cisa kev · ssvc activeExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
3%
EPSS %ILE
84%
KEV
⚠ Exploited

Published

June 10, 2024

Last Modified

November 5, 2025

Advisory Details (8)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2295a7ef5c8c49241bff769e7826ef2582e532a6
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/051c0bde9f0450a2ec3d62a86d2a0d2fad117f13
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eacb8b195579c174a6d3e12a9690b206eb7f28cf
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/db0082825037794c5dba9959c9de13ca34cc5e72
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8af8e6118a6605f0e495a58d591ca94a85a50fc
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92f1655aa2b2294d0b49925f3b875a634bd3b59e
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81dd3c82a456b0015461754be7cb2693991421b4
generic

net: fix __dst_negative_advice() race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5af198c387128a9d2ddd620b0f0803564a4d4508

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.121.110) @ jammy2026-07-26ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-07-26ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.230.242~16.04.1) @ xenial2026-07-26ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1182.197~16.04.1) @ xenial2026-07-26ubuntu
redhatkpatch-patch2024-08-26redhat
redhatrhcos-414.92.202408100542-02024-08-22redhat
redhatrhcos-415.92.202408100433-02024-08-22redhat
redhatrhcos-413.92.202408122222-02024-08-22redhat
redhatrhcos-416.94.202408132101-02024-08-20redhat
redhatrhcos-412.86.202408091913-02024-08-19redhat
redhatkernel-0:5.14.0-427.31.1.el9_42024-08-15redhat
redhatkernel-0:4.18.0-193.138.1.el8_22024-08-14redhat
redhatkernel-rt-0:5.14.0-284.79.1.rt14.364.el9_22024-08-14redhat
redhatkernel-0:5.14.0-284.79.1.el9_22024-08-14redhat
redhatkernel-0:5.14.0-70.112.1.el9_02024-08-13redhat
redhatkernel-rt-0:5.14.0-70.112.1.rt21.184.el9_02024-08-13redhat
redhatkernel-0:3.10.0-1062.90.1.el72024-08-13redhat
redhatkernel-rt-0:4.18.0-305.138.1.rt7.214.el8_42024-08-13redhat
redhatkernel-0:4.18.0-305.138.1.el8_42024-08-13redhat
redhatkernel-0:3.10.0-1160.123.1.el72024-08-13redhat
redhatkernel-0:4.18.0-477.67.1.el8_82024-08-13redhat
redhatkernel-0:4.18.0-372.118.1.el8_62024-08-13redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 65× in last 7d / 371× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 759 total refreshes for this CVE.

  1. 2026-07-27 11:14 UTCVendor advisory
  2. 2026-07-27 11:14 UTCGHSA enrichment
  3. 2026-07-27 07:05 UTCVendor advisory
  4. 2026-07-27 07:05 UTCGHSA enrichment
  5. 2026-07-27 02:56 UTCVendor advisory
  6. 2026-07-27 02:55 UTCGHSA enrichment
  7. 2026-07-26 22:45 UTCVendor advisory
  8. 2026-07-26 22:45 UTCGHSA enrichment
  9. 2026-07-26 18:36 UTCEG score recompute
  10. 2026-07-26 18:36 UTCVendor advisory
  11. 2026-07-26 18:36 UTCGHSA enrichment
  12. 2026-07-26 14:53 UTCEPSS rescore
  13. 2026-07-26 14:24 UTCEG score recompute
  14. 2026-07-26 14:24 UTCVendor advisory
  15. 2026-07-26 14:24 UTCGHSA enrichment
  16. 2026-07-26 10:14 UTCVendor advisory
  17. 2026-07-26 10:14 UTCGHSA enrichment
  18. 2026-07-26 06:05 UTCVendor advisory
  19. 2026-07-26 06:04 UTCGHSA enrichment
  20. 2026-07-26 01:53 UTCEG score recompute
  21. 2026-07-26 01:53 UTCVendor advisory
  22. 2026-07-26 01:53 UTCGHSA enrichment
  23. 2026-07-25 14:16 UTCEPSS rescore
  24. 2026-07-24 14:16 UTCEPSS rescore
  25. 2026-07-23 14:17 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 14:17 UTCEPSS rescore
  2. 2026-07-23 02:38 UTCEG score recompute
  3. 2026-07-22 20:24 UTCVendor advisory
  4. 2026-07-22 20:23 UTCGHSA enrichment
  5. 2026-07-22 19:40 UTCCISA KEV update
  6. 2026-07-22 16:13 UTCEG score recompute
  7. 2026-07-22 16:13 UTCVendor advisory
  8. 2026-07-22 16:13 UTCGHSA enrichment
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-22 12:03 UTCVendor advisory
  12. 2026-07-22 12:03 UTCGHSA enrichment
  13. 2026-07-22 07:53 UTCVendor advisory
  14. 2026-07-22 07:53 UTCGHSA enrichment
  15. 2026-07-22 03:43 UTCVendor advisory
  16. 2026-07-22 03:43 UTCGHSA enrichment
  17. 2026-07-21 23:32 UTCVendor advisory
  18. 2026-07-21 23:32 UTCGHSA enrichment
  19. 2026-07-21 18:15 UTCEG score recompute
  20. 2026-07-21 18:15 UTCVendor advisory
  21. 2026-07-21 18:15 UTCGHSA enrichment
  22. 2026-07-21 15:23 UTCEPSS rescore
  23. 2026-07-21 15:23 UTCEPSS rescore
  24. 2026-07-21 14:37 UTCCISA KEV update
  25. 2026-07-21 14:06 UTCVendor advisory
  26. 2026-07-21 14:06 UTCGHSA enrichment
  27. 2026-07-21 09:56 UTCVendor advisory
  28. 2026-07-21 09:56 UTCGHSA enrichment
  29. 2026-07-21 05:46 UTCVendor advisory
  30. 2026-07-21 05:45 UTCGHSA enrichment
  31. 2026-07-21 01:34 UTCVendor advisory
  32. 2026-07-21 01:34 UTCGHSA enrichment
  33. 2026-07-20 21:24 UTCVendor advisory
  34. 2026-07-20 21:24 UTCGHSA enrichment
  35. 2026-07-20 17:15 UTCEG score recompute
  36. 2026-07-20 17:15 UTCVendor advisory
  37. 2026-07-20 17:14 UTCGHSA enrichment
  38. 2026-07-20 17:06 UTCEPSS rescore
  39. 2026-07-20 13:04 UTCVendor advisory
  40. 2026-07-20 13:04 UTCGHSA enrichment
  41. 2026-07-20 08:55 UTCVendor advisory
  42. 2026-07-20 08:54 UTCGHSA enrichment
  43. 2026-07-20 04:44 UTCVendor advisory
  44. 2026-07-20 04:44 UTCGHSA enrichment
  45. 2026-07-20 00:35 UTCVendor advisory
  46. 2026-07-19 20:25 UTCVendor advisory
  47. 2026-07-19 20:25 UTCGHSA enrichment
  48. 2026-07-19 16:15 UTCEG score recompute
  49. 2026-07-19 16:15 UTCVendor advisory
  50. 2026-07-19 16:15 UTCGHSA enrichment
  51. 2026-07-19 14:30 UTCEPSS rescore
  52. 2026-07-19 14:30 UTCEPSS rescore
  53. 2026-07-19 12:05 UTCVendor advisory
  54. 2026-07-19 12:05 UTCGHSA enrichment
  55. 2026-07-19 07:56 UTCVendor advisory
  56. 2026-07-19 07:56 UTCGHSA enrichment
  57. 2026-07-19 03:46 UTCEG score recompute
  58. 2026-07-19 03:46 UTCVendor advisory
  59. 2026-07-19 03:46 UTCGHSA enrichment
  60. 2026-07-19 02:28 UTCEPSS rescore
  61. 2026-07-19 02:28 UTCEPSS rescore
  62. 2026-07-18 23:36 UTCVendor advisory
  63. 2026-07-18 23:36 UTCGHSA enrichment
  64. 2026-07-18 19:26 UTCVendor advisory
  65. 2026-07-18 19:26 UTCGHSA enrichment
  66. 2026-07-18 15:16 UTCVendor advisory
  67. 2026-07-18 15:16 UTCGHSA enrichment
  68. 2026-07-18 11:06 UTCEG score recompute
  69. 2026-07-18 11:06 UTCVendor advisory
  70. 2026-07-18 11:06 UTCGHSA enrichment
  71. 2026-07-18 10:03 UTCEPSS rescore
  72. 2026-07-18 06:56 UTCVendor advisory
  73. 2026-07-18 06:56 UTCGHSA enrichment
  74. 2026-07-18 02:46 UTCVendor advisory
  75. 2026-07-18 02:46 UTCGHSA enrichment

Frequently asked(6)

What is CVE-2024-36971?
CVE-2024-36971 is a critical vulnerability published on June 10, 2024. In the Linux kernel, the following vulnerability has been resolved: net: fix dstnegativeadvice() race dstnegativeadvice() 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->skdstcache, then call…
When was CVE-2024-36971 disclosed?
CVE-2024-36971 was first published in the National Vulnerability Database on June 10, 2024, with the most recent update on November 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-36971 actively exploited?
Yes. CISA added CVE-2024-36971 to the Known Exploited Vulnerabilities catalog on August 7, 2024, affecting Android Kernel. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2024-36971?
CVE-2024-36971 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2024-36971?
CVE-2024-36971 affects Android Kernel. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2024-36971?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36971, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-36971

Explore →

Is Your Infrastructure Affected by CVE-2024-36971?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.