[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026021429-CVE-2026-23179-6ff7@gregkh>
Date: Sat, 14 Feb 2026 17:28:36 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()
From: Greg Kroah-Hartman <gregkh@...nel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-23179 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.124 with commit f532b29b0e313f42b964014038b0f52899b240ec
Fixed in 6.12.70 with commit 6e0c7503a5803d568d56a9f9bca662cd94a14908
Fixed in 6.18.10 with commit 1c90f930e7b410dd2d75a2a19a85e19c64e98ad5
Fixed in 6.19 with commit 2fa8961d3a6a1c2395d8d560ffed2c782681bade
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-23179
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/nvme/target/tcp.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f532b29b0e313f42b964014038b0f52899b240ec
https://git.kernel.org/stable/c/6e0c7503a5803d568d56a9f9bca662cd94a14908
https://git.kernel.org/stable/c/1c90f930e7b410dd2d75a2a19a85e19c64e98ad5
https://git.kernel.org/stable/c/2fa8961d3a6a1c2395d8d560ffed2c782681bade
Powered by blists - more mailing lists