CVE-2026-23179 json
nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()
published 2026-02-14 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-6111
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.12.70, 6.18.10, 6.19
- linux Debian 13 6.12.73-1
- linux Debian 14 6.18.10-1
debian advisories DEBIAN-CVE-2026-23179
- linux Ubuntu 24.04 LTS 6.8.0-117.117
- linux-aws Ubuntu 24.04 LTS 6.8.0-1055.58
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1058.61
- linux-gke Ubuntu 24.04 LTS 6.8.0-1054.60
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1055.56
- linux-azure Ubuntu 24.04 LTS 6.8.0-1056.62
- linux-gkeop Ubuntu 24.04 LTS 6.8.0-1041.44
- linux-raspi Ubuntu 24.04 LTS 6.8.0-1056.60
ubuntu advisories UBUNTU-CVE-2026-23179
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.34.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.34.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1
- kernel-obs-build SLE Module for Development Tools 15 SP7 6.4.0-150700.53.34.1
- kernel-default-base SLE Module for Basesystem 15 SP7 6.4.0-150700.53.34.1.150700.17.23.1
suse advisories SUSE-SU-2026:1081-1SUSE-SU-2026:20873-1SUSE-SU-2026:20838-1SUSE-SU-2026:20931-1SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.27.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.27.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.27.1
opensuse advisories openSUSE-SU-2026:20416-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-23179 updated cvss 6.5
kernel: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
Sources
- CVE List CVE-2026-23179
- NVD CVE-2026-23179
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.