EUVD-2026-59532
GHSA-33r9-vmmw-q268
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attacker fully controls TCP connection lifecycle and can force non-ESTABLISHED socket state with no credentials; repeated leaks cause availability loss with no confidentiality or integrity impact.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Lifecycle Timeline
5DescriptionCVE.org
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.
AnalysisAI
Resource leakage in the Linux kernel's NVMe-over-TCP target subsystem (nvmet-tcp) allows unauthenticated network clients to exhaust kernel queue and socket resources by manipulating a TLS handshake. The flaw in nvmet_tcp_tls_handshake_done() ignores the return value of nvmet_tcp_set_queue_sock(), so if the socket leaves TCP_ESTABLISHED state during handshake completion - a condition an attacker can induce by timing a connection abort - resources are never cleaned up. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires two explicit configuration prerequisites: (1) the nvmet-tcp kernel module must be loaded and an NVMe-oF target must be actively configured and listening - this is not present in default Linux installations and requires deliberate storage administrator setup; (2) TLS must be the configured transport security mode on that target, since the vulnerable function `nvmet_tcp_tls_handshake_done()` is only invoked in TLS code paths - a plain-TCP nvmet-tcp target is not affected. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5) is credible and consistent with the description: the TLS handshake phase precedes NVMe authentication, so any TCP-reachable client can attempt to trigger the resource leak without credentials. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker with network access to TCP port 4420 on a storage server running nvmet-tcp with TLS connects and initiates a TLS handshake, then abruptly resets the TCP connection at a point that leaves the socket in a non-ESTABLISHED state precisely when the kernel fires the handshake-done callback. This causes `nvmet_tcp_set_queue_sock()` to fail, its error is ignored, and the kernel queue and socket structures are leaked without cleanup. … |
| Remediation | Upgrade the Linux kernel to a patched stable release: version 6.18.40 or 7.1.5, both confirmed by EUVD-2026-59532, or any build from the 7.2-rc1 branch or later. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit systems running nvmet-tcp to identify which have TLS configured and prioritize those for immediate remediation. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today