CVE-2026-98230xfrm: use hlist_del_init_rcu for state_cache and state_cache_input
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.12%, higher than 2% of scored CVEs.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: xfrm: use hlist_del_init_rcu for state_cache and state_cache_input Commit 14acf9652e56 ("xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete") converted bydst/bysrc/byseq/byspi from hlist_del_rcu() to hlist_del_init_rcu() so that a second __xfrm_state_delete() on the same object becomes a no-op rather than a write through LIST_POISON pprev. It missed state_cache and state_cache_input, which kept hlist_del_rcu(): - hlist_del_rcu() leaves pprev = LIST_POISON2 (non-NULL), so hlist_unhashed() returns false. - hlist_del_init_rcu() leaves pprev = NULL, so hlist_unhashed() returns true. A second __xfrm_state_delete() therefore enters __hlist_del() on the already-deleted state_cache/state_cache_input nodes and does WRITE_ONCE(*pprev, next) through LIST_POISON2 — a write use-after-free once the slab is reused. The corruption can in turn cause a subsequent hlist_for_each_entry_rcu traversal to follow a dangling next pointer, producing the read use-after-free reported in xfrm_input_state_lookup(). Switch state_cache and state_cache_input to hlist_del_init_rcu() to match the other four lists, closing the write use-after-free and, with it, the read use-after-free it spawns.
- CVSS
- 7.0 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.12% (percentile 2)
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 7, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from aa48a18fdb0911572d133057cd579db704b87da4 before fb38fb7420d5f7192f9e2b6ac835ede149cd7ac5; from 0045e3d80613cc7174dc15f189ee6fc4e73b9365 before 4748c27e2e6a1969e02f1df46e62f79d2799b80b; 0045e3d80613cc7174dc15f189ee6fc4e73b9365 builds before 9b74a47a4cbd0d29faff4f3b199212c73e6b6220; 0045e3d80613cc7174dc15f189ee6fc4e73b9365 builds before 2afb8dc1f4390f164db8352f8e685e126e9db566; 5e4334dc39443645415450163ff5ff1ee7e79784; from 6.12.13 before 6.12.112 | CNA record |
References
- https://git.kernel.org/stable/c/fb38fb7420d5f7192f9e2b6ac835ede149cd7ac5
- https://git.kernel.org/stable/c/4748c27e2e6a1969e02f1df46e62f79d2799b80b
- https://git.kernel.org/stable/c/9b74a47a4cbd0d29faff4f3b199212c73e6b6220
- https://git.kernel.org/stable/c/2afb8dc1f4390f164db8352f8e685e126e9db566
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.