nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() (CVE-2026-80813) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80813

nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist()

Answer in brief

CVE-2026-80813 records a Unknown severity vulnerability in nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist(). 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.

Published Sep 4, 2026Updated Sep 4, 2026Source checked Sep 4, 2026First seen by HOL Sep 4, 2026Material review Sep 4, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=61c9967cd63448292a64f9ee9aeb6e2053e3a624 <61dc1a37e04d4003a19095f54883358330034a39 \|\| >=61c9967cd63448292a64f9ee9aeb6e2053e3a624 <2bc1e33ff6a558c8ceef7c0077f3ef70a15fcba2 \|\| >=61c9967cd63448292a64f9ee9aeb6e2053e3a624 <123d664ac98d6f3464462ad4a530474b91ba9890 \|\| >=61c9967cd63448292a64f9ee9aeb6e2053e3a624 <79aba4c9403419d822972d2851f2a96a2c0531cf	61dc1a37e04d4003a19095f54883358330034a39, 2bc1e33ff6a558c8ceef7c0077f3ef70a15fcba2, 123d664ac98d6f3464462ad4a530474b91ba9890, 79aba4c9403419d822972d2851f2a96a2c0531cf
Linux/Linuxgeneric	6.13	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 61dc1a37e04d4003a19095f54883358330034a39 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 4, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() When a host issues an Identify command with CNS 07h (Active Namespace ID List for a specific I/O Command Set), nvmet_execute_identify_nslist() is called with match_css set. The command-set filter dereferences req->ns, but this handler never calls nvmet_req_find_ns(), so req->ns is always NULL (nvmet_req_init() resets it to NULL). As soon as an enabled namespace with an NSID greater than the requested value exists, req->ns->csi dereferences a NULL pointer and oopses. Besides the crash, the comparison is logically wrong: to filter the list by command set it must test the command set of the namespace being iterated, not a single fixed value. Use the loop variable ns->csi.

Quoted source text, attributed separately from HOL analysis.