CVE-2026-68426: Linux kernel · Use After Free
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in bbca7cc3b2b4b10afbfee99b81d9ee78f5423046 : patch Linux kernel as a priority.
Data as of 30 Oct 2026, 16:33 UTC
Thin evidence
One scorer or none| CNA (Linux) | CVSS 3.1 | 9.8 |
|---|
- Patch
- Available – fixed in bbca7cc3b2b4b10afbfee99b81d9ee78f5423046, b58731e0570bfd3989999fc2baf9ee4fecd5bec6, 4927ab8a8acc8db4fad33e803d1d35e0b16cef83 +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-68426 (opens in a new tab)
- git.kernel.org/stable/c/33e1b0d25ca0d2818c635ff80e6aa0d295e08a98 (opens in a new tab)
- git.kernel.org/stable/c/3f4c3919baf0944ad96580467c302bc6c7758b00 (opens in a new tab)
- git.kernel.org/stable/c/4927ab8a8acc8db4fad33e803d1d35e0b16cef83 (opens in a new tab)
- git.kernel.org/stable/c/4e695742396be18d5291c310a3d7c450959d647a (opens in a new tab)
- git.kernel.org/stable/c/b58731e0570bfd3989999fc2baf9ee4fecd5bec6 (opens in a new tab)
- git.kernel.org/stable/c/bbca7cc3b2b4b10afbfee99b81d9ee78f5423046 (opens in a new tab)