# CVE-2026-90412: nvmet: fix return status of RMI log page on allocation failure

> An attacker can cause NVMe host requests to fail silently by triggering memory allocation failures, leading to potential 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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-90412, DEBIAN-CVE-2026-90412, GHSA-c4vg-43j9-mh2m, UBUNTU-CVE-2026-90412

## What is CVE-2026-90412?

CVE-2026-90412 is a denial of service vulnerability in Linux, published on 17 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 return status of RMI log page on allocation failure

nvmet_execute_get_log_page_rmi() leaves 'status' holding NVME_SC_SUCCESS
(set by the successful nvmet_req_find_ns() call) when the kzalloc() for
the log buffer fails. It then jumps to the out label and completes the
request with a success status, so the host is told the command succeeded
while no data was transferred.

Initialize 'status' to NVME_SC_INTERNAL, matching the smart log handler,
so an allocation failure is reported as an internal error.

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


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

Apply the vendor's patch.

## Is CVE-2026-90412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90412 is a denial of service vulnerability in Linux, published on 17 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-90412 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-90412/ (Markdown: https://insights.sbomify.com/CVE-2026-90412/index.md)
```

## Sources

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

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