CVE-2026-72429

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:

ipv6: ioam: fix type confusion of dst_entry

IOAM uses a dummy dst_entry(null_dst) to mark that the destination should not be changed after the transformation. This dst is stored in the IOAM lwt state and may be passed to dst_cache_set_ip6().

However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which treats the dst_entry as part of a struct rt6_info. Since the null_dst was embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted in an invalid cast and rt6_get_cookie() reading fields from the wrong object.

In practice, the wrong cookie is not used while dst->obsolete is zero, but rt6_get_cookie() may also access per-cpu value when rt->sernum is zero. In this case, rt->sernum aliases ioam6_lwt::cache::reset_ts, which can become zero, making this a potential invalid pointer access.

Fix this by embedding a full struct rt6_info for the dummy IPv6 route and passing its dst member to the dst APIs.

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
46%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

ipv6: ioam: fix type confusion of dst_entry - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: fix type confusion of dst_entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ed19e11d2146076d117d51a940643990118449b
generic

ipv6: ioam: fix type confusion of dst_entry - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-72429(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 49× in last 7d / 49× 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-21 06:03 UTCGHSA enrichment
  2. 2026-08-21 02:06 UTCEG score recompute
  3. 2026-08-21 02:06 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:09 UTCGHSA enrichment
  6. 2026-08-20 18:13 UTCGHSA enrichment
  7. 2026-08-20 14:17 UTCGHSA enrichment
  8. 2026-08-20 10:21 UTCGHSA enrichment
  9. 2026-08-20 06:25 UTCGHSA enrichment
  10. 2026-08-20 02:29 UTCGHSA enrichment
  11. 2026-08-19 22:32 UTCGHSA enrichment
  12. 2026-08-19 18:35 UTCEG score recompute
  13. 2026-08-19 18:35 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 14:38 UTCGHSA enrichment
  16. 2026-08-19 10:42 UTCGHSA enrichment
  17. 2026-08-19 06:46 UTCGHSA enrichment
  18. 2026-08-19 02:48 UTCGHSA enrichment
  19. 2026-08-18 22:50 UTCGHSA enrichment
  20. 2026-08-18 18:54 UTCGHSA enrichment
  21. 2026-08-18 14:58 UTCEG score recompute
  22. 2026-08-18 14:58 UTCGHSA enrichment
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 10:46 UTCGHSA enrichment
Show 24 more
  1. 2026-08-18 06:50 UTCGHSA enrichment
  2. 2026-08-18 02:53 UTCGHSA enrichment
  3. 2026-08-17 22:56 UTCGHSA enrichment
  4. 2026-08-17 18:59 UTCGHSA enrichment
  5. 2026-08-17 14:21 UTCEG score recompute
  6. 2026-08-17 14:21 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 10:24 UTCEG score recompute
  9. 2026-08-17 10:24 UTCGHSA enrichment
  10. 2026-08-17 06:28 UTCEG score recompute
  11. 2026-08-17 06:28 UTCGHSA enrichment
  12. 2026-08-17 05:57 UTCEG score recompute 9.80
  13. 2026-08-17 05:57 UTCGHSA enrichment
  14. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  15. 2026-08-17 05:29 UTCEG score recompute
  16. 2026-08-17 05:29 UTCGHSA enrichment
  17. 2026-08-17 05:24 UTCMITRE cvelistV5
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 06:33 UTCGHSA enrichment
  22. 2026-08-15 06:23 UTCNVD update
  23. 2026-08-15 06:04 UTCEG score recompute
  24. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72429?
CVE-2026-72429 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: fix type confusion of dst_entry IOAM uses a dummy dstentry(nulldst) to mark that the destination should not be changed after the transformation. This dst is stored in the IOAM lwt state and may be passed to…
When was CVE-2026-72429 disclosed?
CVE-2026-72429 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-72429 actively exploited?
CVE-2026-72429 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 53.6% of all scored CVEs.
What is the CVSS score of CVE-2026-72429?
CVE-2026-72429 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72429, 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-72429

Explore →

Is Your Infrastructure Affected by CVE-2026-72429?

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