CVE-2026-98230

xfrm: use hlist_del_init_rcu for state_cache and state_cache_input

  • High 7.0

Description

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.

Key facts

Published
6 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.118% likely to be exploited in the next 30 days, higher than 1.757% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.0CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • aa48a18fdb0911572d133057cd579db704b87da4 up to but excluding fb38fb7420d5f7192f9e2b6ac835ede149cd7ac5 (affected)
  • 0045e3d80613cc7174dc15f189ee6fc4e73b9365 up to but excluding 4748c27e2e6a1969e02f1df46e62f79d2799b80b (affected)
  • 0045e3d80613cc7174dc15f189ee6fc4e73b9365 up to but excluding 9b74a47a4cbd0d29faff4f3b199212c73e6b6220 (affected)
  • 0045e3d80613cc7174dc15f189ee6fc4e73b9365 up to but excluding 2afb8dc1f4390f164db8352f8e685e126e9db566 (affected)
  • 5e4334dc39443645415450163ff5ff1ee7e79784 (affected)
  • 6.12.13 up to but excluding 6.12.112 (affected)
LinuxLinux
  • Default status: affected
  • 6.13 (affected)
  • 0 up to but excluding 6.13 (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.54 up to and including 6.18.* (unaffected)
  • 7.2.8 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 6 Oct 2026 Published

References