Answer in brief
CVE-2026-74385 records a Unknown severity vulnerability in nvmet-tcp: check return value of nvmet_tcp_set_queue_sock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=675b453e024154dd547921c6e6d5b58747ba7e0e <cba2ee57fd302727aea7d41e9d9cd0969f5df0fb || >=675b453e024154dd547921c6e6d5b58747ba7e0e <22aa70f9a0544643ec37d442b6fcb1833d804462 || >=675b453e024154dd547921c6e6d5b58747ba7e0e <7ef789703e2b91775dcb36b2efa46325be31a2a0 | cba2ee57fd302727aea7d41e9d9cd0969f5df0fb, 22aa70f9a0544643ec37d442b6fcb1833d804462, 7ef789703e2b91775dcb36b2efa46325be31a2a0 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74385 records a Unknown severity vulnerability in nvmet-tcp: check return value of nvmet_tcp_set_queue_sock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=675b453e024154dd547921c6e6d5b58747ba7e0e <cba2ee57fd302727aea7d41e9d9cd0969f5df0fb || >=675b453e024154dd547921c6e6d5b58747ba7e0e <22aa70f9a0544643ec37d442b6fcb1833d804462 || >=675b453e024154dd547921c6e6d5b58747ba7e0e <7ef789703e2b91775dcb36b2efa46325be31a2a0 | cba2ee57fd302727aea7d41e9d9cd0969f5df0fb, 22aa70f9a0544643ec37d442b6fcb1833d804462, 7ef789703e2b91775dcb36b2efa46325be31a2a0 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.