Skip to main content
VulnerabilityPublished Updated

CVE-2026-89972: Linux kernel · nvme: add missing SRCU grace period in error path

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in ef248d5de4469fb6bbaf8dbe0c4c47800080d648 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ef248d5de4469fb6bbaf8dbe0c4c47800080d648, d663944dbad81bb0e3635d7090db4713e6300858, 76023560d60f10b4f808941163aa2975f1631683 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ed754e5deeb17f4e675c84e4b6c640cc7344e498, < ef248d5de4469fb6bbaf8dbe0c4c47800080d648
Fixed in
  • ef248d5de4469fb6bbaf8dbe0c4c47800080d648
LinuxLinuxAffected
  • ≥ ed754e5deeb17f4e675c84e4b6c640cc7344e498, < d663944dbad81bb0e3635d7090db4713e6300858
Fixed in
  • d663944dbad81bb0e3635d7090db4713e6300858
LinuxLinuxAffected
  • ≥ ed754e5deeb17f4e675c84e4b6c640cc7344e498, < 76023560d60f10b4f808941163aa2975f1631683
Fixed in
  • 76023560d60f10b4f808941163aa2975f1631683
LinuxLinuxAffected
  • ≥ ed754e5deeb17f4e675c84e4b6c640cc7344e498, < 3868476cd39161f18720582df17a1b621e805b5d
Fixed in
  • 3868476cd39161f18720582df17a1b621e805b5d
LinuxLinuxAffected
  • ≥ ed754e5deeb17f4e675c84e4b6c640cc7344e498, < 0d4735418512ef825176726eaaa8bd6a35f6b46d
Fixed in
  • 0d4735418512ef825176726eaaa8bd6a35f6b46d
LinuxLinuxAffected
  • =4.15
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: nvme: add missing SRCU grace period in error path nvme_alloc_ns() error path at out_unlink_ns removes ns from the namespace head siblings list with list_del_rcu(&ns->siblings) but does not wait for SRCU readers before freeing the namespace struct. Multipath code iterates the head->list under srcu_read_lock() in nvme_find_path() and nvme_mpath_revalidate_paths(), so a concurrent reader can still hold a reference to ns when kfree(ns) runs. The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.

References

Community reviews

Loading reviews…