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.
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the Linux kernel’s xfrm packet‑processing code causes the skb->prev pointer of a GSO segment list to remain pointing at a segment that has been stolen by asynchronous crypto. The stale pointer is later dereferenced when the list is re‑validated, resulting in a use‑after‑free that can corrupt kernel memory and compromise the integrity of the system. The core weakness is a classic kernel use‑after‑free defect, capable of leading to privilege escalation or denial of service. The description indicates that the attack could be triggered by sending crafted network packets that provoke the async crypto to steal a segment during transmission.

Affected Systems

All Linux kernel builds that contain the vulnerable GSO segment handling logic but do not yet include the patch are affected. The bug was present in kernel sources before the commit that fixes the stale skb->prev issue, and the patch is the official remediation. Exact affected version ranges are not specified, but any kernel released prior to incorporation of the fix is subject to the risk.

Risk and Exploitability

The CVSS score is not listed, but the nature of the exploit—a kernel use‑after‑free—suggests high severity. The EPSS score is not available, and the vulnerability is not in the CISA KEV catalog, indicating no documented widespread exploitation yet. However, an attacker that can send malformed packets to the kernel, potentially from a remote source, could trigger the flaw, making the attack vector likely remote via network traffic. The fix requires kernel patching; until it is applied the vulnerability remains exploitable.

Generated by OpenCVE AI on August 10, 2026 at 16:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that resets skb->prev before returning a GSO segment
  • Upgrade the system to a kernel version that includes this patch
  • If immediate patching is not possible, limit or disable asynchronous crypto on interfaces handling GSO traffic, or block untrusted inbound traffic until the fix is applied

Generated by OpenCVE AI on August 10, 2026 at 16:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 17:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
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.
Title xfrm: fix stale skb->prev after async crypto steals a GSO segment
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-10T12:04:46.945Z

Reserved: 2026-07-30T09:28:09.392Z

Link: CVE-2026-68426

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-11T01:15:04Z

Weaknesses