VulnerabilityPublished 15 Aug 2026Updated 21 Oct 2026

CVE-2026-74385: Linux kernel · nvmet-tcp: check return value of nvmet_tcp_set_queue_sock

Affects Linux kernelSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in cba2ee57fd302727aea7d41e9d9cd0969f5df0fb : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers can reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch

Available – fixed in cba2ee57fd302727aea7d41e9d9cd0969f5df0fb, 41b63ff99e3ef37d08f3693413dae5ede5e79fe1, 22aa70f9a0544643ec37d442b6fcb1833d804462 +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to cba2ee57fd302727aea7d41e9d9cd0969f5df0fb, 41b63ff99e3ef37d08f3693413dae5ede5e79fe1, 22aa70f9a0544643ec37d442b6fcb1833d804462 or 7ef789703e2b91775dcb36b2efa46325be31a2a0.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 675b453e024154dd547921c6e6d5b58747ba7e0e, < cba2ee57fd302727aea7d41e9d9cd0969f5df0fb	Fixed in cba2ee57fd302727aea7d41e9d9cd0969f5df0fb
LinuxLinux	Affected ≥ 675b453e024154dd547921c6e6d5b58747ba7e0e, < 41b63ff99e3ef37d08f3693413dae5ede5e79fe1	Fixed in 41b63ff99e3ef37d08f3693413dae5ede5e79fe1
LinuxLinux	Affected ≥ 675b453e024154dd547921c6e6d5b58747ba7e0e, < 22aa70f9a0544643ec37d442b6fcb1833d804462	Fixed in 22aa70f9a0544643ec37d442b6fcb1833d804462
LinuxLinux	Affected ≥ 675b453e024154dd547921c6e6d5b58747ba7e0e, < 7ef789703e2b91775dcb36b2efa46325be31a2a0	Fixed in 7ef789703e2b91775dcb36b2efa46325be31a2a0
LinuxLinux	Affected =6.7	Fixed in–

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.

References

Community reviews

Loading reviews…