nvme-tcp: don't access released socket during error recovery
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 |
|
|
6.1.186.2.56.3In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: don't access released socket during error recovery
While the error recovery work is temporarily failing reconnect attempts, running the 'nvme list' command causes a kernel NULL pointer dereference by calling getsockname() with a released socket.
During error recovery work, the nvme tcp socket is released and a new one created, so it is not safe to access the socket without proper check.
From the CVE record · Linux
The Linux kernel’s nvme-tcp error recovery can access a released socket while reconnect attempts are failing. A local user running `nvme list` during that window can trigger a kernel NULL pointer dereference; the input does not specify whether authentication beyond local access is required.
Operators running the Linux kernel with nvme-tcp should check their systems; affected versions are not specified.