# xfrm: fix stale skb->prev after async crypto steals a GSO segment

CVE record · `CVE-2026-68426`

- **Identifiers:** `CVE-2026-68426`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 10 Aug 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 10 Aug 2026, 12:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 4e695742396be18d5291c310a3d7c450959d647a` (git)
  - affected: `f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 4927ab8a8acc8db4fad33e803d1d35e0b16cef83` (git)
  - affected: `f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before b58731e0570bfd3989999fc2baf9ee4fecd5bec6` (git)
  - affected: `f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 33e1b0d25ca0d2818c635ff80e6aa0d295e08a98` (git)
  - affected: `f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before bbca7cc3b2b4b10afbfee99b81d9ee78f5423046` (git)
  - affected: `f53c723902d1ac5f0b0a11d7c9dcbff748dde74e to before 3f4c3919baf0944ad96580467c302bc6c7758b00` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.16`
  - unaffected: `before 4.16` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.42 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.6 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel xfrm code, from version 4.16 until fixed releases, can use freed memory after an async crypto operation takes a GSO segment, because a list pointer is left stale. The source gives few details on what an attacker needs to trigger it; its CVSS 3.1 base score is 9.8. Upgrade to 6.1.191, 6.6.160, 6.12.114 or 6.18.42 in the matching series, or to a later release.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0050, the 43rd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 10 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-68426](https://www.cve.org/CVERecord?id=CVE-2026-68426)
- [NVD: CVE-2026-68426](https://nvd.nist.gov/vuln/detail/CVE-2026-68426)

### References from the CNA

- <https://git.kernel.org/stable/c/4e695742396be18d5291c310a3d7c450959d647a>
- <https://git.kernel.org/stable/c/4927ab8a8acc8db4fad33e803d1d35e0b16cef83>
- <https://git.kernel.org/stable/c/b58731e0570bfd3989999fc2baf9ee4fecd5bec6>
- <https://git.kernel.org/stable/c/33e1b0d25ca0d2818c635ff80e6aa0d295e08a98>
- <https://git.kernel.org/stable/c/bbca7cc3b2b4b10afbfee99b81d9ee78f5423046>
- <https://git.kernel.org/stable/c/3f4c3919baf0944ad96580467c302bc6c7758b00>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-68426>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-68426/>. Everything for agents: <https://agentprime.io/llms.txt>.
