LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a hang when NVMe-over-TCP target listener socket handling collides with socket close processing. The available sources describe a deadlock condition, not data theft or privilege escalation. Business urgency depends on whether affected Linux systems expose or operate NVMe/TCP target services.

Executive priority

Treat as a targeted infrastructure reliability issue until more severity data is available. Prioritize patch review for storage platforms using NVMe-over-TCP targets, but do not assume broad internet risk or active exploitation from the provided evidence.

Technical view

The bug is in nvmet-tcp. During TCP_LISTEN socket close handling, a callback flushes outstanding packets and calls nvmet_tcp_listen_data_ready() while sk_callback_lock is already held. The fix checks TCP_LISTEN state before attempting to acquire sk_callback_lock, avoiding deadlock.

Likely exposure

Exposure appears limited to Linux kernels with the nvmet-tcp code path in affected versions, especially systems acting as NVMe-over-TCP targets. The source bundle lists affected Linux versions but lacks full distribution mapping, configuration prerequisites, or package advisories.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not marked KEV. The sources describe a kernel deadlock triggered by socket close/listen-state behavior. Practical exploitability, remote reachability, and required privileges are not stated.

Researcher notes

The record lacks CVSS, CWE, and detailed attack prerequisites. The commit message supports a deadlock/hang impact in a specific kernel callback path. Further analysis should focus on reachability of nvmet_tcp_listen_data_ready() in deployed NVMe/TCP target configurations.

Mitigation direction

  • Update to a kernel or vendor package containing the linked stable fixes.
  • Prioritize systems running NVMe-over-TCP target services.
  • Check Linux distribution advisories for backported fixes and affected package names.
  • If updates are delayed, review vendor guidance for disabling unused nvmet-tcp exposure.

Validation and detection

  • Inventory Linux kernel versions on storage and virtualization hosts.
  • Identify systems loading or configuring nvmet-tcp target functionality.
  • Confirm vendor kernel changelogs include the referenced stable fix commits.
  • Review operational monitoring for kernel hangs affecting NVMe/TCP listeners.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23179 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux675b453e024154dd547921c6e6d5b58747ba7e0e, 675b453e024154dd547921c6e6d5b58747ba7e0e, 675b453e024154dd547921c6e6d5b58747ba7e0eunaffected
LinuxLinux6.7, 0, 6.12.70, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.