Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 1c90f930e7b410dd2d75a2a19a85e19c64e98ad5, 2fa8961d3a6a1c2395d8d560ffed2c782681bade, 6e0c7503a5803d568d56a9f9bca662cd94a14908.

Low priority for now. Upgrade to Linux Linux 1c90f930e7b410dd2d75a2a19a85e19c64e98ad5, 2fa8961d3a6a1c2395d8d560ffed2c782681bade, 6e0c7503a5803d568d56a9f9bca662cd94a14908 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Feb 14, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23179

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.7affected
    • 675b453e024154dd547921c6e6d5b58747ba7e0e and later · before 6e0c7503a5803d568d56a9f9bca662cd94a14908affected · git
    • 675b453e024154dd547921c6e6d5b58747ba7e0e and later · before 1c90f930e7b410dd2d75a2a19a85e19c64e98ad5affected · git
    • 675b453e024154dd547921c6e6d5b58747ba7e0e and later · before 2fa8961d3a6a1c2395d8d560ffed2c782681badeaffected · git
    • before 6.7not affected · semver
    • 6.12.70 and later · up to and including 6.12.*not affected · semver
    • 6.18.10 and later · up to and including 6.18.*not affected · semver
    • 6.19 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.73-16.12.73-1
Debian:14linuxbefore 6.18.10-16.18.10-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-23175Feb 14, 2026 · net: cpsw: Execute ndo_set_rx_mode callback in a work queue
    28Monitor
  • ← EarlierCVE-2026-23177Feb 14, 2026 · mm, shmem: prevent infinite loop on truncate race
    0Monitor
  • Later →CVE-2026-23181Feb 14, 2026 · btrfs: sync read disk super and set block size
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1c90f930e7b410dd2d75a2a19a85e19c64e98ad5Vendor (CNA)
Linux Linux2fa8961d3a6a1c2395d8d560ffed2c782681badeVendor (CNA)
Linux Linux6e0c7503a5803d568d56a9f9bca662cd94a14908Vendor (CNA)
debian:linux6.12.73-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records