Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68426, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.50% · top 57% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected f53c723902d1ac5f0b0a11d7c9dcbff748dde74e – < 4e695742396be18d5291c310a3d7c450959d647a
    • affected f53c723902d1ac5f0b0a11d7c9dcbff748dde74e – < 4927ab8a8acc8db4fad33e803d1d35e0b16cef83
    • affected f53c723902d1ac5f0b0a11d7c9dcbff748dde74e – < b58731e0570bfd3989999fc2baf9ee4fecd5bec6
    • affected f53c723902d1ac5f0b0a11d7c9dcbff748dde74e – < 33e1b0d25ca0d2818c635ff80e6aa0d295e08a98
    • affected f53c723902d1ac5f0b0a11d7c9dcbff748dde74e – < bbca7cc3b2b4b10afbfee99b81d9ee78f5423046
    • affected f53c723902d1ac5f0b0a11d7c9dcbff748dde74e – < 3f4c3919baf0944ad96580467c302bc6c7758b00
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68426 badge
[![CVE-2026-68426](https://cveledger.app/badge/CVE-2026-68426.svg)](https://cveledger.app/cve/CVE-2026-68426)

Record last updated .