BaselineWatch
Desk

CVE-2026-68426

9.8 critical SSVC exploitation: none Published

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.

Fix

Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.

Change history 6

  1. StatusReceived → PublishedNVD modified 2026-10-21 12:44
  2. References+2 references (now 5)NVD modified 2026-10-21 13:19
  3. StatusPublished → ReceivedNVD modified 2026-10-21 13:19
  4. StatusReceived → PublishedNVD modified 2026-10-19 21:09
  5. CwesCWE-416NVD modified 2026-10-19 22:17
  6. First seenCVSS 9.8NVD modified 2026-10-16 16:19

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 5