CVE-2026-68426

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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 — Patch released 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.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Oct 5, 2026
Patch available.
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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu
redhatkernel-0:5.14.0-570.146.1.el9_62026-10-01redhat
redhatkernel-rt-0:4.18.0-553.164.1.rt7.505.el8_102026-09-17redhat
redhatkernel-0:4.18.0-553.164.1.el8_102026-09-17redhat
redhatkernel-0:5.14.0-687.49.1.el9_82026-09-17redhat
redhatkernel-0:6.12.0-211.55.1.el10_22026-09-15redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 44× in last 7d / 217× 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 383 total refreshes for this CVE.

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

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 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.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68426?
CVE-2026-68426 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68426?
A fix for CVE-2026-68426 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68426 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.