nvme-fabrics: use reserved tag for reg read/write command
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvme-fabrics: use reserved tag for reg read/write command
In some scenarios, if too many commands are issued by nvme command in the same time by user tasks, this may exhaust all tags of admin_q. If a reset (nvme reset or IO timeout) occurs before these commands finish, reconnect routine may fail to update nvme regs due to insufficient tags, which will cause kernel hang forever. In order to workaround this issue, maybe we can let reg_read32()/reg_read64()/reg_write32() use reserved tags. This maybe safe for nvmf:
1. For the disable ctrl path, we will not issue connect command 2. For the enable ctrl / fw activate path, since connect and reg_xx() are called serially.
So the reserved tags may still be enough while reg_xx() use reserved tags.
From the CVE record · Linux
The Linux kernel’s nvme-fabrics code can run out of admin queue tags when user tasks issue many NVMe commands at once. If an NVMe reset or I/O timeout occurs before those commands finish, the reconnect routine may be unable to update NVMe registers, causing the kernel to hang. This requires local command activity and a reset or timeout.
Engineers running Linux kernels with nvme-fabrics should check whether their kernel includes the fix; affected versions were not provided.