CVE-2026-68426

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-55612 (ENISA EUVD) · GHSA-g9mw-m3g9-8x3m (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%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
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

October 30, 2026

Advisory Details (6)

Auto-updated Nov 14, 2026
Patch available.
Web page

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
Web page

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/b58731e0570bfd3989999fc2baf9ee4fecd5bec6
Web page

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/4e695742396be18d5291c310a3d7c450959d647a
Web page

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/4927ab8a8acc8db4fad33e803d1d35e0b16cef83
Web page

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
Web page

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(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute2026-11-18ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1025.26) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-11-18ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-11-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2022.23) @ resolute2026-11-18ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-11-18ubuntu
redhatkernel-rt-0:5.14.0-284.197.1.rt14.482.el9_22026-10-14redhat
redhatkernel-0:5.14.0-284.197.1.el9_22026-10-12redhat
redhatkernel-0:4.18.0-372.220.1.el8_62026-10-07redhat
redhatkernel-0:5.14.0-427.154.1.el9_42026-10-07redhat
redhatkernel-0:4.18.0-305.211.1.el8_42026-10-07redhat
redhatkernel-0:4.18.0-477.172.1.el8_82026-10-07redhat
redhatkernel-0:6.12.0-55.108.1.el10_02026-10-05redhat
redhatkernel-0:5.14.0-570.146.1.el9_62026-10-01redhat
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-rt-0:4.18.0-553.164.1.rt7.505.el8_102026-09-17redhat
redhatkernel-0:6.12.0-211.55.1.el10_22026-09-15redhat
linuxKernel @ 6.1.191 (fixes >=4.16.0)—osv

These rows come from Ubuntu, Red Hat and OSV. 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.3~rc7-1~exp1 (375 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (164 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 20× in last 7d / 90× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 585 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 485 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 08:36 UTCEchelonGraph re-scored
  2. 2026-11-22 08:36 UTCVendor advisory
  3. 2026-11-22 08:36 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-11-21 07:49 UTCEchelonGraph re-scored
  6. 2026-11-21 07:49 UTCVendor advisory
  7. 2026-11-21 07:49 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-11-20 07:04 UTCEchelonGraph re-scored
  10. 2026-11-20 07:04 UTCVendor advisory
  11. 2026-11-20 07:04 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-11-19 06:18 UTCEchelonGraph re-scored
  14. 2026-11-19 06:18 UTCVendor advisory
  15. 2026-11-19 06:18 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-11-18 05:33 UTCEchelonGraph re-scored
  18. 2026-11-18 05:33 UTCVendor advisory
  19. 2026-11-18 05:33 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-11-17 04:48 UTCEchelonGraph re-scored
  22. 2026-11-17 04:48 UTCVendor advisory
  23. 2026-11-17 04:47 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-11-16 03:32 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-16 03:32 UTCVendor advisory
  2. 2026-11-16 03:32 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-15 17:02 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-15 01:23 UTCEchelonGraph re-scored
  5. 2026-11-15 01:23 UTCVendor advisory
  6. 2026-11-15 01:23 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-11-14 00:33 UTCEchelonGraph re-scored
  9. 2026-11-14 00:33 UTCVendor advisory
  10. 2026-11-14 00:33 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-11-12 23:46 UTCEchelonGraph re-scored
  13. 2026-11-12 23:46 UTCVendor advisory
  14. 2026-11-12 23:46 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-11-11 23:01 UTCEchelonGraph re-scored
  17. 2026-11-11 23:01 UTCVendor advisory
  18. 2026-11-11 23:01 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-11-10 22:15 UTCEchelonGraph re-scored
  21. 2026-11-10 22:15 UTCVendor advisory
  22. 2026-11-10 22:15 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-11-09 21:15 UTCEchelonGraph re-scored
  25. 2026-11-09 21:15 UTCVendor advisory
  26. 2026-11-09 21:15 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-11-08 20:30 UTCEchelonGraph re-scored
  29. 2026-11-08 20:30 UTCVendor advisory
  30. 2026-11-08 20:30 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-11-07 19:43 UTCEchelonGraph re-scored
  33. 2026-11-07 19:43 UTCVendor advisory
  34. 2026-11-07 19:43 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-11-06 18:57 UTCEchelonGraph re-scored
  37. 2026-11-06 18:57 UTCVendor advisory
  38. 2026-11-06 18:57 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  40. 2026-11-06 15:55 UTCOSV refresh
  41. 2026-11-05 18:12 UTCEchelonGraph re-scored
  42. 2026-11-05 18:12 UTCVendor advisory
  43. 2026-11-05 18:12 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-11-04 17:26 UTCEchelonGraph re-scored
  46. 2026-11-04 17:26 UTCVendor advisory
  47. 2026-11-04 17:26 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-11-03 16:40 UTCEchelonGraph re-scored
  51. 2026-11-03 16:40 UTCVendor advisory
  52. 2026-11-03 16:40 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-11-02 15:44 UTCEchelonGraph re-scored
  55. 2026-11-02 15:44 UTCVendor advisory
  56. 2026-11-02 15:44 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  58. 2026-11-01 14:59 UTCEchelonGraph re-scored
  59. 2026-11-01 14:59 UTCVendor advisory
  60. 2026-11-01 14:58 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-10-31 14:13 UTCEchelonGraph re-scored
  63. 2026-10-31 14:13 UTCVendor advisory
  64. 2026-10-31 14:13 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  66. 2026-10-30 13:27 UTCEchelonGraph re-scored
  67. 2026-10-30 13:27 UTCVendor advisory
  68. 2026-10-30 13:27 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-30 12:42 UTCEchelonGraph re-scored
  70. 2026-10-30 12:42 UTCVendor advisory
  71. 2026-10-30 12:41 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-29 22:15 UTCEchelonGraph re-scored
  73. 2026-10-29 22:15 UTCVendor advisory
  74. 2026-10-29 22:14 UTCGHSA enrichmentGHSA-g9mw-m3g9-8x3m · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile

Frequently asked(5)

What is CVE-2026-68426?
CVE-2026-68426 is a critical-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2026-68426 published?
The CVE record for CVE-2026-68426 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-68426 actively exploited?
CVE-2026-68426 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd 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.