CVE-2026-68426: xfrm: fix stale skb->prev after async crypto steals a GSO segment
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 validatexmitskblist() relies on when it sets its tail pointer (tail = skb->prev).
When validatexmitxfrm() 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. validatexmitskblist() later does tail->next = skb, writing through that stale pointer -- a use-after-free.
Repoint skb->prev at the last retained segment before returning.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68426?
CVE-2026-68426 has a risk rating of 55, indicating a moderate severity level.
How do I fix CVE-2026-68426?
To fix CVE-2026-68426, update your Linux kernel to the latest version where the vulnerability has been resolved.
What type of vulnerability is CVE-2026-68426?
CVE-2026-68426 is classified as a 'Use After Free' vulnerability.
What components are affected by CVE-2026-68426?
CVE-2026-68426 affects the xfrm subsystem in the Linux kernel.
When was CVE-2026-68426 published?
CVE-2026-68426 was published on August 10, 2026.