Answer in brief
CVE-2026-89972 records a Unknown severity vulnerability in nvme: add missing SRCU grace period in error path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ed754e5deeb17f4e675c84e4b6c640cc7344e498 <d663944dbad81bb0e3635d7090db4713e6300858 || >=ed754e5deeb17f4e675c84e4b6c640cc7344e498 <76023560d60f10b4f808941163aa2975f1631683 || >=ed754e5deeb17f4e675c84e4b6c640cc7344e498 <ef248d5de4469fb6bbaf8dbe0c4c47800080d648 | d663944dbad81bb0e3635d7090db4713e6300858, 76023560d60f10b4f808941163aa2975f1631683, ef248d5de4469fb6bbaf8dbe0c4c47800080d648 |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.