CVE-2026-64132

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

ipv6: ioam: refresh hdr pointer before ioam6_event()

Reported by Sashiko:

In ipv6_hop_ioam(), the hdr pointer is initialized to point into the skb's linear data buffer. Later, the code calls skb_ensure_writable(), which might reallocate the buffer:

if (skb_ensure_writable(skb, optoff + 2 + hdr->opt_len)) goto drop;

/* Trace pointer may have changed */ trace = (struct ioam6_trace_hdr *)(skb_network_header(skb) + optoff + sizeof(*hdr));

ioam6_fill_trace_data(skb, ns, trace, true);

ioam6_event(IOAM6_EVENT_TRACE, dev_net(skb->dev), GFP_ATOMIC, (void *)trace, hdr->opt_len - 2);

If the skb is cloned or lacks sufficient linear headroom, skb_ensure_writable() will invoke pskb_expand_head(), which reallocates the skb's data buffer and frees the old one, invalidating pointers to it. While the code recalculates the trace pointer immediately after the call to skb_ensure_writable(), it fails to recalculate the hdr pointer.

This patch fixes the above by recalculating the hdr pointer before passing hdr->opt_len to ioam6_event(), so that we avoid any UaF.

CVSS v3
9.8
EG Score
9.8(medium)
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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (4)

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

ipv6: ioam: refresh hdr pointer before ioam6_event() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: ioam: refresh hdr pointer before ioam6_event() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/769723124b7c3b2bfea4cf68ad292698b87c8d01
generic

ipv6: ioam: refresh hdr pointer before ioam6_event() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5af905aa8e91ff8d94572a1e089558f21dcf24ed
generic

ipv6: ioam: refresh hdr pointer before ioam6_event() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24de676da63c1122d2c13b0d546238b66d1b4e62

Vendor Advisories for CVE-2026-64132(1)

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

Patch Availability(5)

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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 62× in last 7d / 364× 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 441 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64132?
CVE-2026-64132 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: ioam: refresh hdr pointer before ioam6_event() Reported by Sashiko: In ipv6hopioam(), the hdr pointer is initialized to point into the skb's linear data buffer. Later, the code calls skbensurewritable(), which might…
When was CVE-2026-64132 disclosed?
CVE-2026-64132 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64132 actively exploited?
CVE-2026-64132 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64132?
CVE-2026-64132 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64132?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64132, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64132

Explore →

Is Your Infrastructure Affected by CVE-2026-64132?

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