In 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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/76d54bf20cdcc1ed7569a89885e09636e9a8d71d Patch
- https://git.kernel.org/stable/c/d82f762db4776fa11de88018f0f5de2d5db72a72 Patch
- https://git.kernel.org/stable/c/fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.5 · linuxNVD modified 2026-10-15 22:17
Affected (CPE criteria) 1
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*