In the Linux kernel, the function nvmet_tcp_set_queue_sock() is called during an NVMe‑over‑TCP TLS handshake. The code currently ignores its return value. If the call fails—for example, when the socket has not reached the TCP_ESTABLISHED state, the subsequent socket callbacks are never installed, and the queue and socket objects are leaked. This unchecked failure can lead to a gradual depletion of kernel queue structures and TCP sockets.

The vulnerability affects the Linux kernel overall, as indicated by the Vendor: Linux and the CPE string for the Linux kernel. No specific kernel release is listed; therefore any kernel that includes the unpatched nvmet‑tcp implementation is potentially affected. Administrators should verify whether their kernel version contains the commit that introduced the check.

The CVSS score is 7.5 and the EPSS score is < 1%, but the vulnerability can result in resource exhaustion and a denial‑of‑service condition if an attacker can repeatedly initiate NVMe‑over‑TCP connections that trigger the faulty handshake. Based on the description, it is inferred that the attacker would need network access to the NVMe target or a privileged local user that can trigger the handshake, making the attack vector likely network‑based. The vulnerability is not listed in CISA's KEV catalog at present, so no known exploits have been reported yet.