Answer in brief
CVE-2026-98153 records a Unknown severity vulnerability in nvme: fix racy access to FDP placement id array. 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 | >=30b5f20bb2ddab013035399e5c7e6577da49320a <e0a23e3c8c4c3ce11529fa70d2292b4e56d143ba || >=30b5f20bb2ddab013035399e5c7e6577da49320a <56e1c6bbe4bb084d7ecf61698afdf70be23dd35f | e0a23e3c8c4c3ce11529fa70d2292b4e56d143ba, 56e1c6bbe4bb084d7ecf61698afdf70be23dd35f |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: nvme: fix racy access to FDP placement id array nvme_query_fdp_info() is called per-path and therefore prone to races. It populates head->nr_plids/head->plids for fdp registration. But nothing protects that pair from concurrent access - two paths scanning the same namespace can race to populate it. Avoid the race by moving this initialization work to nvme_alloc_ns_head() which is called once per shared namespace.
Quoted source text, attributed separately from HOL analysis.