# CVE-2026-74385: nvmet-tcp: check return value of nvmet_tcp_set_queue_sock

> An attacker can cause resource leakage and potential denial of service in the Linux kernel's NVMe over TCP module by triggering a socket state failure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-74385, DEBIAN-CVE-2026-74385, GHSA-33r9-vmmw-q268, UBUNTU-CVE-2026-74385

## What is CVE-2026-74385?

CVE-2026-74385 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-74385?


## How do I fix CVE-2026-74385?

Apply the vendor's patch.

## Is CVE-2026-74385 being exploited?

There is no known exploitation of CVE-2026-74385 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74385 and fix it if it is affected.

What it is: CVE-2026-74385 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74385 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74385/ (Markdown: https://insights.sbomify.com/CVE-2026-74385/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74385
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74385
- OSV: https://osv.dev/vulnerability/CVE-2026-74385

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74385/
Summaries are generated and may contain mistakes; the official description above is the record.