CVE-2026-68426

xfrm: fix stale skb->prev after async crypto steals a GSO segment

State
Published
Severity
9.8 Critical
Published
Aug 10, 2026
Updated
Oct 30, 2026
Reserved
Jul 30, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 4e695742396be18d5291c310a3d7c450959d647aAffected
  • f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 4927ab8a8acc8db4fad33e803d1d35e0b16cef83Affected
  • f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before b58731e0570bfd3989999fc2baf9ee4fecd5bec6Affected
  • f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 33e1b0d25ca0d2818c635ff80e6aa0d295e08a98Affected
  • f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before bbca7cc3b2b4b10afbfee99b81d9ee78f5423046Affected
  • f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 3f4c3919baf0944ad96580467c302bc6c7758b00Affected
LinuxLinux
  • 4.16Affected
  • before 4.16Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.114 through 6.12.*Not affected
  • 6.18.42 through 6.18.*Not affected
  • 7.1.6 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.