| 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: <2025121632-CVE-2025-68218-4aee@gregkh> Date: Tue, 16 Dec 2025 14:57:37 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-68218: nvme-multipath: fix lockdep WARN due to partition scan work From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: nvme-multipath: fix lockdep WARN due to partition scan work Blktests test cases nvme/014, 057 and 058 fail occasionally due to a lockdep WARN. As reported in the Closes tag URL, the WARN indicates that a deadlock can happen due to the dependency among disk->open_mutex, kblockd workqueue completion and partition_scan_work completion. To avoid the lockdep WARN and the potential deadlock, cut the dependency by running the partition_scan_work not by kblockd workqueue but by nvme_wq. The Linux kernel CVE team has assigned CVE-2025-68218 to this issue. Affected and fixed versions =========================== Issue introduced in 6.1.118 with commit 60de2e03f984cfbcdc12fa552f95087c35a05a98 and fixed in 6.1.159 with commit 89456dab7ba5ab63d60945440926673a3205e829 Issue introduced in 6.6.62 with commit 4a57f42e5ed42cb8f1beb262c4f6d3e698939e4e and fixed in 6.6.118 with commit e2a897ad5f538d314955c747a0a2edb184fcdecd Issue introduced in 6.12 with commit 1f021341eef41e77a633186e9be5223de2ce5d48 and fixed in 6.12.60 with commit ef4ab2a8abe554379e10303ae86f7c501336ba0d Issue introduced in 6.12 with commit 1f021341eef41e77a633186e9be5223de2ce5d48 and fixed in 6.17.10 with commit b03eb63288a8ffe3adfb34e68309c8e2edb06d0b Issue introduced in 6.12 with commit 1f021341eef41e77a633186e9be5223de2ce5d48 and fixed in 6.18 with commit 6d87cd5335784351280f82c47cc8a657271929c3 Issue introduced in 6.11.9 with commit a91b7eddf45afeeb9c5ece11dddff5de0921b00f 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-68218 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/host/multipath.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/89456dab7ba5ab63d60945440926673a3205e829 https://git.kernel.org/stable/c/e2a897ad5f538d314955c747a0a2edb184fcdecd https://git.kernel.org/stable/c/ef4ab2a8abe554379e10303ae86f7c501336ba0d https://git.kernel.org/stable/c/b03eb63288a8ffe3adfb34e68309c8e2edb06d0b https://git.kernel.org/stable/c/6d87cd5335784351280f82c47cc8a657271929c3
Powered by blists - more mailing lists