nvme-tcp: don't access released socket during error recovery
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 76d54bf20cdcc1ed7569a89885e09636e9a8d71d, Kernel d82f762db4776fa11de88018f0f5de2d5db72a72 and Kernel fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.1, >=02c57a82c0081141abc19150beab48ef47f97f18 <76d54bf20cdcc1ed7569a89885e09636e9a8d71d, >=02c57a82c0081141abc19150beab48ef47f97f18 <d82f762db4776fa11de88018f0f5de2d5db72a72, >=02c57a82c0081141abc19150beab48ef47f97f18 <fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d | 76d54bf20cdcc1ed7569a89885e09636e9a8d71d, d82f762db4776fa11de88018f0f5de2d5db72a72, fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket