nvmet-tcp: check return value of nvmet_tcp_set_queue_sock
- 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.12.114, 6.18.40, 7.1.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: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock The return value of nvmet_tcp_set_queue_sock() is currently ignored in nvmet_tcp_tls_handshake_done(). If it fails (e.g., due to the socket not being in TCP_ESTABLISHED state), the socket callbacks will not be properly set, leading to queue and socket leakage. Fix this by capturing the return value and calling nvmet_tcp_schedule_release_queue() on failure to ensure proper cleanup.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 675b453e024154dd547921c6e6d5b58747ba7e0e · fixed in 41b63ff99e3ef37d08f3693413dae5ede5e79fe1; From 675b453e024154dd547921c6e6d5b58747ba7e0e · fixed in cba2ee57fd302727aea7d41e9d9cd0969f5df0fb; From 675b453e024154dd547921c6e6d5b58747ba7e0e · fixed in 22aa70f9a0544643ec37d442b6fcb1833d804462; From 675b453e024154dd547921c6e6d5b58747ba7e0e · fixed in 7ef789703e2b91775dcb36b2efa46325be31a2a0
- Linux Linux
6.7
- KernelLinux
From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5