nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e399441de9115cd472b8ace6c517708273ca7997 · < bd764baf82bb46e958a0bd0b481630dd71313055| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
In the Linux kernel’s nvme-fc request initialization, a failed rsp_iu DMA mapping leaves the cmd_iu mapping in place, leaking it for each affected operation. The input does not describe an attacker, exploitation conditions, or authentication or user-interaction requirements.
Engineers running Linux systems that use nvme-fc should check their kernel versions; affected versions were not specified.