CVE-2026-74385
Received Received - Intake

Memory Leak in Linux Kernel NVMe-TCP

Publication date: 2026-08-15

Last updated on: 2026-08-15

Assigner: kernel.org

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-15
Generated
2026-08-15
AI Q&A
2026-08-15
EPSS Evaluated
N/A
NVD
CVE-2026-74385
EUVD
EUVD-2026-59532

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in the Linux kernel's nvmet-tcp module. It occurs when the return value of nvmet_tcp_set_queue_sock() is ignored during a TLS handshake. If the function fails, socket callbacks are not set properly, causing queue and socket leaks.

Impact Analysis

This could lead to resource exhaustion on affected systems due to leaked queues and sockets. It may cause performance degradation or system instability if exploited repeatedly.

Mitigation Strategies

Apply the Linux kernel patch that fixes the nvmet-tcp issue by ensuring nvmet_tcp_set_queue_sock() return values are checked and proper cleanup is performed on failure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-74385. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart