CVE-2026-98370
xfrm: fix compat ALLOCSPI request use-after-free
No known exploitation. EPSS puts it in the 6th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 5f3eea6b7e8f58cf5c8a9d4b9679dc19e9e67ba3, < 494f2bee9d8d0ebcfa249ac41bed7fed26d119b4Upgrade to: 494f2bee9d8d0ebcfa249ac41bed7fed26d119b4Affected: ≥ 5f3eea6b7e8f58cf5c8a9d4b9679dc19e9e67ba3, < 17893987e52918c23945c42e47e894a936305a25Upgrade to: 17893987e52918c23945c42e47e894a936305a25Affected: ≥ 5f3eea6b7e8f58cf5c8a9d4b9679dc19e9e67ba3, < 42971ea17c7a8afc0bdd5ca40648bf4e5bb7b810Upgrade to: 42971ea17c7a8afc0bdd5ca40648bf4e5bb7b810Affected: ≥ 5f3eea6b7e8f58cf5c8a9d4b9679dc19e9e67ba3, < 2b63341e2ebc9b6f73cbd9214dbe7d46dd98c718Upgrade to: 2b63341e2ebc9b6f73cbd9214dbe7d46dd98c718 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: xfrm: fix compat ALLOCSPI request use-after-free xfrm_state_netlink() builds the ALLOCSPI response with dump_one_state(), which already calls alloc_compat() with the response skb and header. xfrm_alloc_userspi() then calls alloc_compat() again, but passes the original request skb and its header. For a compat request, the translator therefore interprets the 228-byte compat xfrm_userspi_info as the 232-byte native layout and reads four bytes past the declared payload. It also publishes the translated child through the request's frag_list. A multicast clone of the request shares skb_shared_info and can observe that child. xfrm_user_rcv_msg() frees it after the request handler returns, racing a compat receiver which may still be copying from it and resulting in a use-after-free. Remove the redundant conversion. The response keeps its correct compat translation from dump_one_state(), and no child is attached to the inbound request.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 6th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/17893987e52918c23945c42e47e894a936305a25
- git.kernel.org/stable/c/248433942155b42a0ef04a5806c8aca024ea7c33
- git.kernel.org/stable/c/2b63341e2ebc9b6f73cbd9214dbe7d46dd98c718
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI