| 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: <2025092359-CVE-2025-39870-2af3@gregkh> Date: Tue, 23 Sep 2025 08:01:01 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-39870: dmaengine: idxd: Fix double free in idxd_setup_wqs() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix double free in idxd_setup_wqs() The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle. It's simpler to just re-write it in a cleaner way. The issues here are: 1) If "idxd->max_wqs" is <= 0 then we call put_device(conf_dev) when "conf_dev" hasn't been initialized. 2) If kzalloc_node() fails then again "conf_dev" is invalid. It's either uninitialized or it points to the "conf_dev" from the previous iteration so it leads to a double free. It's better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations. I also renamed the labels to describe what the goto does and not where the goto was located. The Linux kernel CVE team has assigned CVE-2025-39870 to this issue. Affected and fixed versions =========================== Issue introduced in 6.1.140 with commit d584acdf54f409cb7eae1359ae6c12aaabedeed8 and fixed in 6.1.153 with commit 25e6146c2812487a88f619d5ff6efbdcd5b2bc31 Issue introduced in 6.6.92 with commit 47846211998a9ffb0fcc08092eb95ac783d2b11a and fixed in 6.6.107 with commit df82c7901513fd0fc738052a8e6a330d92cc8ec9 Issue introduced in 6.12.30 with commit 5fcd392dae6d6aba7dc64ffdbb838ff191315da3 and fixed in 6.12.48 with commit ec5430d090d0b6ace8fefa290fc37e88930017d2 Issue introduced in 6.15 with commit 3fd2f4bc010cdfbc07dd21018dc65bd9370eb7a4 and fixed in 6.16.8 with commit 9f0e225635475b2285b966271d5e82cba74295b1 Issue introduced in 6.15 with commit 3fd2f4bc010cdfbc07dd21018dc65bd9370eb7a4 and fixed in 6.17-rc6 with commit 39aaa337449e71a41d4813be0226a722827ba606 Issue introduced in 6.14.8 with commit ed2c66000aa64c0d2621864831f0d04c820a1441 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-39870 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/dma/idxd/init.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/25e6146c2812487a88f619d5ff6efbdcd5b2bc31 https://git.kernel.org/stable/c/df82c7901513fd0fc738052a8e6a330d92cc8ec9 https://git.kernel.org/stable/c/ec5430d090d0b6ace8fefa290fc37e88930017d2 https://git.kernel.org/stable/c/9f0e225635475b2285b966271d5e82cba74295b1 https://git.kernel.org/stable/c/39aaa337449e71a41d4813be0226a722827ba606
Powered by blists - more mailing lists