CVE-2026-90411

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

N/A
Published: September 17, 2026 at 04:09 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.10e399441de9115cd472b8ace6c517708273ca7997
Vendor states this is fixed in 18c5781ed8bc2f423c26ec93e47e2057cd76a783 (fixed)
Vendor states this is fixed in 5e820d04c241c81a47e1940349018690e93d8167 (fixed)
Vendor states this is fixed in acc173608ca7abe5dee8983086b44efd8b0dbc84 (fixed)
Vendor states this is fixed in bb0251991420c25e3ceeac40ea09250d79ed7ef0 (fixed)
Vendor states this is fixed in bd764baf82bb46e958a0bd0b481630dd71313055 (fixed)
Vendor states this is fixed in be5eb47ee3fea338efae1a5b678d6bb5f0fcc931 (fixed)
Vendor states this is fixed in c0892cfb60a75e2c86ba8e2127b133f6549c12b3 (fixed)
Vendor states this is fixed in f49d0c3a8d56a7cda1628ae17341a4a42063563c (fixed)
Vendor states this is fixed in 4.10 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card