CVE-2026-68426

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 — 3 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

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 stale skb->prev after async crypto steals a GSO segment

skb_gso_segment() leaves the segment list head with ->prev pointing at the last segment, an invariant validate_xmit_skb_list() relies on when it sets its tail pointer (tail = skb->prev).

When validate_xmit_xfrm() walks a GSO list and some segments are stolen by async crypto (->xmit() returns -EINPROGRESS), those segments are unlinked from the list but the head ->prev is never updated. If the last segment is the one stolen, the returned head still has ->prev pointing at it, even though it is now owned by the crypto engine and may be freed. validate_xmit_skb_list() later does tail->next = skb, writing through that stale pointer -- a use-after-free.

Repoint skb->prev at the last retained segment before returning.

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

xfrm: fix stale skb->prev after async crypto steals a GSO segment - kernel/git/stable/linux.git - Linux kernel stable tree

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

xfrm: fix stale skb->prev after async crypto steals a GSO segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f4c3919baf0944ad96580467c302bc6c7758b00
generic

xfrm: fix stale skb->prev after async crypto steals a GSO segment - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33e1b0d25ca0d2818c635ff80e6aa0d295e08a98

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

Frequently asked(5)

What is CVE-2026-68426?
CVE-2026-68426 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: xfrm: fix stale skb->prev after async crypto steals a GSO segment skbgsosegment() leaves the segment list head with ->prev pointing at the last segment, an invariant validatexmitskb_list() relies on when it sets its tail pointer…
When was CVE-2026-68426 disclosed?
CVE-2026-68426 was first published in the National Vulnerability Database on August 10, 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-68426 actively exploited?
CVE-2026-68426 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 70.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68426?
CVE-2026-68426 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68426?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68426, 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-68426

Explore →

Is Your Infrastructure Affected by CVE-2026-68426?

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