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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusReceived → PublishedNVD modified 2026-10-21 12:45
- References+1 references (now 4)NVD modified 2026-10-21 13:19
- StatusPublished → ReceivedNVD modified 2026-10-21 13:19
- StatusReceived → PublishedNVD modified 2026-10-21 12:45
- First seenCVSS 7.5NVD modified 2026-10-16 19:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.