Bug 2516837 (CVE-2026-74385)

Summary: CVE-2026-74385 kernel: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the `nvmet-tcp` component of the Linux kernel. This vulnerability arises from ignoring the return value of a function during the TLS handshake, specifically when the network socket is not in an established state. This oversight prevents proper cleanup, leading to the leakage of queues and sockets. An attacker could potentially exploit this issue to cause resource exhaustion, resulting in a Denial of Service (DoS).
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-15 06:36:05 UTC 
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.
Comment 1 Keith Grant 2026-08-20 19:57:20 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026081506-CVE-2026-74385-b03d@gregkh/T