CVE-2026-72451

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

xfrm: Fix xfrm state cache insertion race

The xfrm input state cache insertion code checks the validity of the state before acquiring the global xfrm_state_lock. Thus it's possible for someone else to kill the state after it passed the validity check, and then the insertion will add the dead state to the cache.

Fix this by moving the validity check inside the lock.

This entire function is called on the input path, where BH must be off (e.g., the caller of this function xfrm_input acquires its spinlocks without disabling BH).

So there is no need to disable BH here or take the RCU read lock. Remove both and replace them with an assertion that trips if BH is accidentally enabled on some future calling path.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

xfrm: Fix xfrm state cache insertion race - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: Fix xfrm state cache insertion race - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: Fix xfrm state cache insertion race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dab4dec9a49121d079981ac913569f232c06b06
generic

xfrm: Fix xfrm state cache insertion race - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/041859fd55c81ea55e76d051e39b7b79975b8c7d

Vendor Advisories for CVE-2026-72451(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 45× in last 7d / 45× 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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:41 UTCGHSA enrichment
  3. 2026-08-20 17:52 UTCGHSA enrichment
  4. 2026-08-20 14:03 UTCGHSA enrichment
  5. 2026-08-20 09:41 UTCGHSA enrichment
  6. 2026-08-20 05:52 UTCGHSA enrichment
  7. 2026-08-20 02:03 UTCGHSA enrichment
  8. 2026-08-19 22:14 UTCGHSA enrichment
  9. 2026-08-19 18:24 UTCEG score recompute
  10. 2026-08-19 18:24 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 14:02 UTCGHSA enrichment
  13. 2026-08-19 10:12 UTCGHSA enrichment
  14. 2026-08-19 06:20 UTCGHSA enrichment
  15. 2026-08-19 02:28 UTCGHSA enrichment
  16. 2026-08-18 22:36 UTCGHSA enrichment
  17. 2026-08-18 18:47 UTCGHSA enrichment
  18. 2026-08-18 14:58 UTCEG score recompute
  19. 2026-08-18 14:58 UTCGHSA enrichment
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 10:17 UTCGHSA enrichment
  23. 2026-08-18 06:28 UTCGHSA enrichment
  24. 2026-08-18 02:38 UTCGHSA enrichment
  25. 2026-08-17 22:49 UTCGHSA enrichment
Show 20 more
  1. 2026-08-17 18:59 UTCGHSA enrichment
  2. 2026-08-17 14:06 UTCEG score recompute
  3. 2026-08-17 14:06 UTCGHSA enrichment
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 10:17 UTCEG score recompute
  6. 2026-08-17 10:17 UTCGHSA enrichment
  7. 2026-08-17 06:28 UTCEG score recompute
  8. 2026-08-17 06:28 UTCGHSA enrichment
  9. 2026-08-17 05:57 UTCEG score recompute 9.80
  10. 2026-08-17 05:57 UTCGHSA enrichment
  11. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  12. 2026-08-17 05:28 UTCEG score recompute
  13. 2026-08-17 05:28 UTCGHSA enrichment
  14. 2026-08-17 05:24 UTCMITRE cvelistV5
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 06:23 UTCNVD update
  19. 2026-08-15 06:04 UTCEG score recompute
  20. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72451?
CVE-2026-72451 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: Fix xfrm state cache insertion race The xfrm input state cache insertion code checks the validity of the state before acquiring the global xfrmstatelock. Thus it's possible for someone else to kill the state after it passed…
When was CVE-2026-72451 disclosed?
CVE-2026-72451 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72451 actively exploited?
CVE-2026-72451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all scored CVEs.
What is the CVSS score of CVE-2026-72451?
CVE-2026-72451 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72451?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72451, 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-2026-72451

Explore →

Is Your Infrastructure Affected by CVE-2026-72451?

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