CVE-2026-68127

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-10. 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: 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:

ila: reload IPv6 header after pskb_may_pull in checksum adjust

ila_csum_adjust_transport() caches ip6h = ipv6_hdr(skb) before calling pskb_may_pull(). On a non-linear skb whose transport header sits in a page fragment, pskb_may_pull() can call __pskb_pull_tail() / pskb_expand_head() and free the old skb head, leaving ip6h dangling; the following get_csum_diff(ip6h, p) then reads freed memory. ila_update_ipv6_locator() uses ip6h (and the iaddr derived from it) again after the csum-adjust call and additionally writes the new locator through that pointer.

Impact: a remote IPv6 packet routed through a configured ILA csum-adjust-transport route or receive-side mapping triggers a slab-use-after-free in ila_update_ipv6_locator() (KASAN). The route or mapping requires CAP_NET_ADMIN to configure, but trigger packets are unauthenticated once it exists.

Reload ip6h after each pskb_may_pull() in ila_csum_adjust_transport() before the csum-diff read. In ila_update_ipv6_locator() only the ILA_CSUM_ADJUST_TRANSPORT case pulls the skb, so reload ip6h and iaddr in that case alone before the destination-address write; the neutral-map modes never pull and keep their cached pointers.

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

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (8)

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

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

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

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

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

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

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

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

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

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/896a9512d0d83c2a4b357e5585b7b62a8e3f95c1
generic

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7097a0280b178237265681be66d1bef11d15894b
generic

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/472aba2603ca74c4f7722cb0c0296942b0776b8d
generic

ila: reload IPv6 header after pskb_may_pull in checksum adjust - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1eadcb43893b897ade85ac5bf5c618054bc3c655

Vendor Advisories for CVE-2026-68127(2)

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 60× in last 7d / 74× 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:47 UTCVendor advisory
  2. 2026-08-21 06:47 UTCGHSA enrichment
  3. 2026-08-21 02:39 UTCEG score recompute
  4. 2026-08-21 02:39 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 22:32 UTCGHSA enrichment
  7. 2026-08-20 18:25 UTCGHSA enrichment
  8. 2026-08-20 14:17 UTCGHSA enrichment
  9. 2026-08-20 09:59 UTCGHSA enrichment
  10. 2026-08-20 05:52 UTCGHSA enrichment
  11. 2026-08-20 01:44 UTCGHSA enrichment
  12. 2026-08-19 21:36 UTCGHSA enrichment
  13. 2026-08-19 17:26 UTCEG score recompute
  14. 2026-08-19 17:26 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 16:55 UTCEG score recompute
  17. 2026-08-19 16:55 UTCGHSA enrichment
  18. 2026-08-19 14:37 UTCGHSA enrichment
  19. 2026-08-19 10:12 UTCGHSA enrichment
  20. 2026-08-19 06:01 UTCGHSA enrichment
  21. 2026-08-19 01:51 UTCGHSA enrichment
  22. 2026-08-18 21:40 UTCGHSA enrichment
  23. 2026-08-18 17:25 UTCEG score recompute
  24. 2026-08-18 17:25 UTCGHSA enrichment
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 49 more
  1. 2026-08-18 11:52 UTCGHSA enrichment
  2. 2026-08-18 07:44 UTCGHSA enrichment
  3. 2026-08-18 03:37 UTCGHSA enrichment
  4. 2026-08-17 23:29 UTCGHSA enrichment
  5. 2026-08-17 19:22 UTCGHSA enrichment
  6. 2026-08-17 13:55 UTCEG score recompute
  7. 2026-08-17 13:55 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 09:48 UTCGHSA enrichment
  10. 2026-08-17 05:41 UTCEG score recompute
  11. 2026-08-17 05:41 UTCGHSA enrichment
  12. 2026-08-17 05:11 UTCEG score recompute
  13. 2026-08-17 05:11 UTCGHSA enrichment
  14. 2026-08-17 01:40 UTCGHSA enrichment
  15. 2026-08-16 21:33 UTCGHSA enrichment
  16. 2026-08-16 17:26 UTCEG score recompute
  17. 2026-08-16 17:26 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 13:18 UTCGHSA enrichment
  20. 2026-08-16 09:11 UTCGHSA enrichment
  21. 2026-08-16 05:03 UTCEG score recompute
  22. 2026-08-16 05:03 UTCGHSA enrichment
  23. 2026-08-16 00:56 UTCGHSA enrichment
  24. 2026-08-15 20:49 UTCGHSA enrichment
  25. 2026-08-15 16:42 UTCGHSA enrichment
  26. 2026-08-15 12:35 UTCGHSA enrichment
  27. 2026-08-15 08:28 UTCGHSA enrichment
  28. 2026-08-15 04:21 UTCEG score recompute
  29. 2026-08-15 04:21 UTCGHSA enrichment
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-15 00:13 UTCGHSA enrichment
  32. 2026-08-14 20:06 UTCGHSA enrichment
  33. 2026-08-14 15:59 UTCGHSA enrichment
  34. 2026-08-14 11:52 UTCGHSA enrichment
  35. 2026-08-14 07:45 UTCGHSA enrichment
  36. 2026-08-14 03:38 UTCEG score recompute
  37. 2026-08-14 03:38 UTCGHSA enrichment
  38. 2026-08-13 23:31 UTCEG score recompute
  39. 2026-08-13 23:31 UTCGHSA enrichment
  40. 2026-08-13 22:46 UTCEG score recompute▲ 9.80
  41. 2026-08-13 22:46 UTCGHSA enrichment
  42. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  43. 2026-08-13 22:00 UTCEPSS rescore
  44. 2026-08-13 15:18 UTCEG score recompute
  45. 2026-08-13 15:18 UTCGHSA enrichment
  46. 2026-08-12 13:51 UTCEPSS rescore
  47. 2026-08-10 13:24 UTCNVD update
  48. 2026-08-10 12:21 UTCEG score recompute
  49. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68127?
CVE-2026-68127 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: ila: reload IPv6 header after pskbmaypull in checksum adjust ilacsumadjusttransport() caches ip6h = ipv6hdr(skb) before calling pskbmaypull(). On a non-linear skb whose transport header sits in a page fragment, pskbmaypull() can…
When was CVE-2026-68127 disclosed?
CVE-2026-68127 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68127 actively exploited?
CVE-2026-68127 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 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-68127?
CVE-2026-68127 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68127, 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-68127

Explore →

Is Your Infrastructure Affected by CVE-2026-68127?

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

Start Free Scan →Browse All CVEs