nvme-rdma: fix -EIO cleanup order in queue_rq
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 62eca39722fd997e3621fc903229917b9f0fb271 · < 171b993a4aed9889159df4815b6a6ba141e61975| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvme-rdma: fix -EIO cleanup order in queue_rq
On -EIO, the RDMA queue_rq path reports a host path error and then still cleans up the command and unmaps the SQE DMA. The path error helper completes the request, so that is double cleanup and DMA unmap after the request is already complete.
Unmap the SQE first, then report the host path error. Skip the outer command cleanup on that path.
From the CVE record · Linux
The Linux kernel's nvme-rdma queue_rq path can clean up a command twice and unmap SQE DMA after a request has completed when it encounters -EIO. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel with nvme-rdma should check their systems; affected versions are not specified.