Resource exhaustion via leaked command DMA mappings
Published Sep 17, 2026 · Updated Sep 17, 2026
A DMA mapping leak in Linux nvme-fc allows local users to exhaust kernel resources when response mapping fails during request initialization. The __nvme_fc_init_request() function leaves cmd_iu mapped after rsp_iu mapping fails, and blk-mq skips the exit_request callback on initialization failure. Exploitation requires the NVMe Fibre Channel path and response DMA mapping failures; no specific crash, hang, or reboot outcome is documented.
Summary
What happened
A DMA mapping leak in Linux nvme-fc allows local users to exhaust kernel resources when response mapping fails during request initialization. The __nvme_fc_init_request() function leaves cmd_iu mapped after rsp_iu mapping fails, and blk-mq skips the exit_request callback on initialization failure. Exploitation requires the NVMe Fibre Channel path and response DMA mapping failures; no specific crash, hang, or reboot outcome is documented.
The record
- CVE
- CVE-2026-90411
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-772, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.10
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <18c5781ed8bc2f423c26ec93e47e2057cd76a783
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <5e820d04c241c81a47e1940349018690e93d8167
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <acc173608ca7abe5dee8983086b44efd8b0dbc84
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <bb0251991420c25e3ceeac40ea09250d79ed7ef0
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <bd764baf82bb46e958a0bd0b481630dd71313055
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <be5eb47ee3fea338efae1a5b678d6bb5f0fcc931
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <c0892cfb60a75e2c86ba8e2127b133f6549c12b3
- Affected versionversion=e399441de9115cd472b8ace6c517708273ca7997 <f49d0c3a8d56a7cda1628ae17341a4a42063563c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started