nvme: add missing SRCU grace period in error path
Affects the Linux kernel NVMe driver in the 4.15.0 to 6.6.160, 6.7.0 to 6.12.112, 6.13.0 to 6.18.51 and 6.19.0 to 7.2.5 ranges. Fixed in 6.6.160, 6.12.112, 6.18.51 and 7.2.5.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Linux kernel's NVMe storage driver, specifically its namespace setup error path and multipath handling, is affected. A namespace structure can be freed while a concurrent reader still holds a reference to it, which could lead to memory corruption or a crash.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ed754e5deeb17f4e675c84e4b6c640cc7344e498 · fixed in 3868476cd39161f18720582df17a1b621e805b5d; From ed754e5deeb17f4e675c84e4b6c640cc7344e498 · fixed in 0d4735418512ef825176726eaaa8bd6a35f6b46d; From ed754e5deeb17f4e675c84e4b6c640cc7344e498 · fixed in d663944dbad81bb0e3635d7090db4713e6300858; From ed754e5deeb17f4e675c84e4b6c640cc7344e498 · fixed in 76023560d60f10b4f808941163aa2975f1631683; From ed754e5deeb17f4e675c84e4b6c640cc7344e498 · fixed in ef248d5de4469fb6bbaf8dbe0c4c47800080d648
- Linux Linux
4.15
- KernelLinux
From 4.15.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5
References 5
Questions about CVE-2026-89972
What does this mean?
When creating an NVMe namespace fails, the kernel frees the namespace structure without waiting for a read-side grace period. A concurrent multipath reader can still hold a reference to that structure after it is freed.Source: git.kernel.org
Am I affected, and how do I check?
Kernels from 4.15.0 up to 6.6.160, from 6.7.0 up to 6.12.112, from 6.13.0 up to 6.18.51, and from 6.19.0 up to 7.2.5 are in the affected ranges. Check the running version with uname -r and compare it against these ranges.Source: git.kernel.org
What should I do about it?
Update to the fixed stable release for your branch: 6.6.160, 6.12.112, 6.18.51, or 7.2.5 or later. The advisory does not list a workaround.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data