What is CVE-2026-68426?

CVE-2026-68426 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10, affecting Linux kernel versions from 4.16 onward and patched in 6.18.42, 7.1.6 and 7.2. CVE-2026-68426 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-68426?

CVE-2026-68426 has a CVSS score of 9.8 out of 10, rated Critical severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-68426?

Yes, CVE-2026-68426 has been patched. Fixed versions include 6.18.42, 7.1.6 and 7.2. If you are running Linux kernel 4.16 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-68426 actively exploited?

CVE-2026-68426 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-68426

Critical

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.

Package Linux Kernel

Published 2026-08-10

Last modified 2026-08-17

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

9.8

out of 10

Critical

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 4.16 and later are affected. Fixed in 6.18.42, 7.1.6, 7.2 and their respective stable series.

Affected from

≥ 4.16

Fixed in

✓ 6.18.42 6.18.x ✓ 7.1.6 7.1.x ✓ 7.2

References

3 total

Details

CVE ID CVE-2026-68426

Severity Critical

CVSS score 9.8 / 10

CVSS version 3.1

Published 2026-08-10

Modified 2026-08-17

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-68426?

CVE-2026-68426 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10 . It affects Linux kernel versions from 4.16 onward and has been patched in 6.18.42, 7.1.6 and 7.2. CVE-2026-68426 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-68426?

CVE-2026-68426 has a CVSS score of 9.8 out of 10, rated Critical severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-68426?

Yes. CVE-2026-68426 has been patched. Fixed versions include 6.18.42, 7.1.6 and 7.2. If you are running Linux kernel 4.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-68426 actively exploited?

No. CVE-2026-68426 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.