CVE-2026-68426: xfrm: fix stale skb->prev after async crypto steals a GSO segment

Published Aug 10, 2026
·
Updated

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.

Other sources

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.

— IBM

Affected Software

3 affected components
Linux Kernel
IBM QRadar<=7.6.0.0 - 7.6.0.4
IBM QRadar<=7.5.0 - 7.5.0 UP16 IF01

Event History

Aug 10, 2026
CVE Published
via MITRE·12:04 PM
Data Sourced
via MITRE·12:04 PM
DescriptionSeverity
Data Sourced
via NVD·01:20 PM
DescriptionSeverity
Aug 11, 2026
Data Sourced
via Microsoft·08:12 AM
DescriptionSeverityWeakness
Oct 13, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-68426?

CVE-2026-68426 has a risk rating of 55, indicating a moderate severity level.

2

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.

3

What type of vulnerability is CVE-2026-68426?

CVE-2026-68426 is classified as a 'Use After Free' vulnerability.

4

What components are affected by CVE-2026-68426?

CVE-2026-68426 affects the xfrm subsystem in the Linux kernel.

5

When was CVE-2026-68426 published?

CVE-2026-68426 was published on August 10, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203