# CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist()

> A remote attacker can crash the Linux kernel by sending a specific NVMe Identify command, causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-80813, DEBIAN-CVE-2026-80813, GHSA-rf7w-4fpm-954r, UBUNTU-CVE-2026-80813

## What is CVE-2026-80813?

CVE-2026-80813 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80813?


## How do I fix CVE-2026-80813?

Apply the vendor's patch.

## Is CVE-2026-80813 being exploited?

There is no known exploitation of CVE-2026-80813 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80813 and fix it if it is affected.

What it is: CVE-2026-80813 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80813 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80813/ (Markdown: https://insights.sbomify.com/CVE-2026-80813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80813
- OSV: https://osv.dev/vulnerability/CVE-2026-80813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80813/
Summaries are generated and may contain mistakes; the official description above is the record.