nvme-tcp: don't access released socket during error recovery
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.18, 6.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 02c57a82c0081141abc19150beab48ef47f97f18 · fixed in fe2d9e54165dadaa0d0cc3355c0be9c3e129fa0d; From 02c57a82c0081141abc19150beab48ef47f97f18 · fixed in d82f762db4776fa11de88018f0f5de2d5db72a72; From 02c57a82c0081141abc19150beab48ef47f97f18 · fixed in 76d54bf20cdcc1ed7569a89885e09636e9a8d71d
- Linux Linux
6.1
- KernelLinux
From 6.1.0 · fixed in 6.1.18; From 6.2.0 · fixed in 6.2.5