Bug 2513477 (CVE-2026-68426) - CVE-2026-68426 kernel: xfrm: fix stale skb->prev after async crypto steals a GSO segment
Summary: CVE-2026-68426 kernel: xfrm: fix stale skb->prev after async crypto steals a ...
Keywords:
Status: NEW
Alias: CVE-2026-68426
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-10 12:39 UTC by OSIDB Bzimport
Modified: 2026-08-13 10:34 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-10 12:39:33 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-08-11 08:02:58 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081053-CVE-2026-68426-9cce@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.