CVE-2026-90411: nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 18c5781ed8bc2f423c26ec93e47e2057cd76a783, 5e820d04c241c81a47e1940349018690e93d8167, acc173608ca7abe5dee8983086b44efd8b0dbc84; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 18c5781ed8bc2f423c26ec93e47e2057cd76a783, 5e820d04c241c81a47e1940349018690e93d8167, acc173608ca7abe5dee8983086b44efd8b0dbc84; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.10affected
- e399441de9115cd472b8ace6c517708273ca7997 and later · before c0892cfb60a75e2c86ba8e2127b133f6549c12b3affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before 5e820d04c241c81a47e1940349018690e93d8167affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before bb0251991420c25e3ceeac40ea09250d79ed7ef0affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before acc173608ca7abe5dee8983086b44efd8b0dbc84affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before 18c5781ed8bc2f423c26ec93e47e2057cd76a783affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before bd764baf82bb46e958a0bd0b481630dd71313055affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before be5eb47ee3fea338efae1a5b678d6bb5f0fcc931affected · git
- e399441de9115cd472b8ace6c517708273ca7997 and later · before f49d0c3a8d56a7cda1628ae17341a4a42063563caffected · git
- before 4.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90409Sep 17, 2026 · drm/panthor: Add vm_bind region with kbo range overlap check0Monitor
- ← EarlierCVE-2026-90410Sep 17, 2026 · spi: davinci: switch to managed controller allocation0Monitor
- Later →CVE-2026-90412Sep 17, 2026 · nvmet: fix return status of RMI log page on allocation failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 18c5781ed8bc2f423c26ec93e47e2057cd76a783 | Vendor (CNA) |
| Linux Linux | 5e820d04c241c81a47e1940349018690e93d8167 | Vendor (CNA) |
| Linux Linux | acc173608ca7abe5dee8983086b44efd8b0dbc84 | Vendor (CNA) |
| Linux Linux | bb0251991420c25e3ceeac40ea09250d79ed7ef0 | Vendor (CNA) |
| Linux Linux | bd764baf82bb46e958a0bd0b481630dd71313055 | Vendor (CNA) |
| Linux Linux | be5eb47ee3fea338efae1a5b678d6bb5f0fcc931 | Vendor (CNA) |
| Linux Linux | c0892cfb60a75e2c86ba8e2127b133f6549c12b3 | Vendor (CNA) |
| Linux Linux | f49d0c3a8d56a7cda1628ae17341a4a42063563c | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5e820d04c241c81a47e1940349018690e93d8167
- git.kernel.org/stable/c/acc173608ca7abe5dee8983086b44efd8b0dbc84
- git.kernel.org/stable/c/bb0251991420c25e3ceeac40ea09250d79ed7ef0
- git.kernel.org/stable/c/bd764baf82bb46e958a0bd0b481630dd71313055
- git.kernel.org/stable/c/be5eb47ee3fea338efae1a5b678d6bb5f0fcc931
- git.kernel.org/stable/c/c0892cfb60a75e2c86ba8e2127b133f6549c12b3
- git.kernel.org/stable/c/f49d0c3a8d56a7cda1628ae17341a4a42063563c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.