# CVE-2026-90411: nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request

> A memory leak in the Linux kernel NVMe FC driver can lead to resource exhaustion and denial of service when DMA mapping fails.

- **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:** AZL-102372, BELL-CVE-2026-90411, DEBIAN-CVE-2026-90411, GHSA-cp4g-4cx8-r2fq, UBUNTU-CVE-2026-90411

## What is CVE-2026-90411?

CVE-2026-90411 is a memory corruption 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:

nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request

__nvme_fc_init_request() maps cmd_iu and then rsp_iu for DMA. If the
rsp_iu mapping fails, the original code only recorded the error and fell
through: it left the already-mapped cmd_iu unmapped and still marked the
op as FCPOP_STATE_IDLE before returning. Since blk-mq does not call
.exit_request() when .init_request() fails, the cmd_iu mapping is leaked
for every op whose rsp_iu mapping fails.

Jump to an error path on rsp_iu mapping failure that unmaps cmd_iu and
returns the error without marking the op idle, so it stays in the
FCPOP_STATE_UNINIT state set by the initial memset().

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


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

Apply the vendor's patch.

## Is CVE-2026-90411 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90411 is a memory corruption 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-90411 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-90411/ (Markdown: https://insights.sbomify.com/CVE-2026-90411/index.md)
```

## Sources

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

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