CVE-2026-68426

CVE CVE-2026-68426EUVD EUVD-2026-55612Published 2026-08-10T12:04:46.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux f53c723902d1ac5f0b0a11d7c9dcbff748dde74e <bbca7cc3b2b4b10afbfee99b81d9ee78f5423046; f53c723902d1ac5f0b0a11d7c9dcbff748dde74e <3f4c3919baf0944ad96580467c302bc6c7758b00; f53c723902d1ac5f0b0a11d7c9dcbff748dde74e <33e1b0d25ca0d2818c635ff80e6aa0d295e08a98; patch: 7.1.6; patch: 7.2-rc4; 4.16; patch: 6.18.42; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.