| 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
| ||
|
Message-ID: <2025111259-CVE-2025-40171-0cb5@gregkh> Date: Wed, 12 Nov 2025 05:46:58 -0500 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-40171: nvmet-fc: move lsop put work to nvmet_fc_ls_req_op From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: move lsop put work to nvmet_fc_ls_req_op It’s possible for more than one async command to be in flight from __nvmet_fc_send_ls_req. For each command, a tgtport reference is taken. In the current code, only one put work item is queued at a time, which results in a leaked reference. To fix this, move the work item to the nvmet_fc_ls_req_op struct, which already tracks all resources related to the command. The Linux kernel CVE team has assigned CVE-2025-40171 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15.150 with commit 5e0bc09a52b6169ce90f7ac6e195791adb16cec4 and fixed in 5.15.195 with commit 11269c08013f4ee8b8f5edc6c56700acb34092d0 Issue introduced in 6.1.80 with commit 9e6987f8937a7bd7516aa52f25cb7e12c0c92ee8 and fixed in 6.1.156 with commit a28112cc55013cd8cbd5d36b5115a5b851151bd9 Issue introduced in 6.6.19 with commit eaf0971fdabf2a93c1429dc6bedf3bbe85dffa30 and fixed in 6.6.112 with commit 060ecc81240ef9d60d9485a3a5eb55a0d6e7a25c Issue introduced in 6.8 with commit 710c69dbaccdac312e32931abcb8499c1525d397 and fixed in 6.12.53 with commit 7331925c247b03b7767b8cd93cfe1b7aa2377850 Issue introduced in 6.8 with commit 710c69dbaccdac312e32931abcb8499c1525d397 and fixed in 6.17.3 with commit 7a619f8c869117ffed08365b377f66b7e1d941b4 Issue introduced in 6.8 with commit 710c69dbaccdac312e32931abcb8499c1525d397 and fixed in 6.18-rc1 with commit db5a5406fb7e5337a074385c7a3e53c77f2c1bd3 Issue introduced in 6.7.7 with commit 1d86f79287206deec36d63b89c741cf542b6cadd 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-40171 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/11269c08013f4ee8b8f5edc6c56700acb34092d0 https://git.kernel.org/stable/c/a28112cc55013cd8cbd5d36b5115a5b851151bd9 https://git.kernel.org/stable/c/060ecc81240ef9d60d9485a3a5eb55a0d6e7a25c https://git.kernel.org/stable/c/7331925c247b03b7767b8cd93cfe1b7aa2377850 https://git.kernel.org/stable/c/7a619f8c869117ffed08365b377f66b7e1d941b4 https://git.kernel.org/stable/c/db5a5406fb7e5337a074385c7a3e53c77f2c1bd3
Powered by blists - more mailing lists