# CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()

> A remote attacker can cause a kernel hang in the NVMe over TCP target by closing a listening socket, leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2026-23179, DEBIAN-CVE-2026-23179, GHSA-g782-c42f-q4q3, ROOT-OS-DEBIAN-13-CVE-2026-23179, ROOT-OS-UBUNTU-2204-CVE-2026-23179, ROOT-OS-UBUNTU-2404-CVE-2026-23179, UBUNTU-CVE-2026-23179

## What is CVE-2026-23179?

CVE-2026-23179 is a denial of service vulnerability in Linux, published on 14 Feb 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: fixup hang in nvmet_tcp_listen_data_ready()

When the socket is closed while in TCP_LISTEN a callback is run to
flush all outstanding packets, which in turns calls
nvmet_tcp_listen_data_ready() with the sk_callback_lock held.
So we need to check if we are in TCP_LISTEN before attempting
to get the sk_callback_lock() to avoid a deadlock.

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


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

Apply the vendor's patch.

## Is CVE-2026-23179 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23179 is a denial of service vulnerability in Linux, published on 14 Feb 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-23179 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-23179/ (Markdown: https://insights.sbomify.com/CVE-2026-23179/index.md)
```

## Sources

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

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