linux-cve-announce - CVE-2025-40343: nvmet-fc: avoid scheduling association deletion twice

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025120912-CVE-2025-40343-dbb0@gregkh>
Date: Tue,  9 Dec 2025 13:10:25 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40343: nvmet-fc: avoid scheduling association deletion twice

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

nvmet-fc: avoid scheduling association deletion twice

When forcefully shutting down a port via the configfs interface,
nvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and
then nvmet_disable_port(). Both functions will eventually schedule all
remaining associations for deletion.

The current implementation checks whether an association is about to be
removed, but only after the work item has already been scheduled. As a
result, it is possible for the first scheduled work item to free all
resources, and then for the same work item to be scheduled again for
deletion.

Because the association list is an RCU list, it is not possible to take
a lock and remove the list entry directly, so it cannot be looked up
again. Instead, a flag (terminating) must be used to determine whether
the association is already in the process of being deleted.

The Linux kernel CVE team has assigned CVE-2025-40343 to this issue.

Affected and fixed versions
===========================

	Fixed in 5.15.197 with commit 2f4852db87e25d4e226b25cb6f652fef9504360e
	Fixed in 6.1.159 with commit 85e2ce1920cb511d57aae59f0df6ff85b28bf04d
	Fixed in 6.6.117 with commit 601ed47b2363c24d948d7bac0c23abc8bd459570
	Fixed in 6.12.58 with commit 04d17540ef51e2c291eb863ca87fd332259b2d40
	Fixed in 6.17.8 with commit c09ac9a63fc3aaf4670ad7b5e4f5afd764424154
	Fixed in 6.18 with commit f2537be4f8421f6495edfa0bc284d722f253841d

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-2025-40343
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/fc.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/2f4852db87e25d4e226b25cb6f652fef9504360e
	https://git.kernel.org/stable/c/85e2ce1920cb511d57aae59f0df6ff85b28bf04d
	https://git.kernel.org/stable/c/601ed47b2363c24d948d7bac0c23abc8bd459570
	https://git.kernel.org/stable/c/04d17540ef51e2c291eb863ca87fd332259b2d40
	https://git.kernel.org/stable/c/c09ac9a63fc3aaf4670ad7b5e4f5afd764424154
	https://git.kernel.org/stable/c/f2537be4f8421f6495edfa0bc284d722f253841d