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: <2025070342-CVE-2025-38171-a380@gregkh> Date: Thu, 3 Jul 2025 10:36:27 +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-38171: power: supply: max77705: Fix workqueue error handling in probe From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: power: supply: max77705: Fix workqueue error handling in probe The create_singlethread_workqueue() doesn't return error pointers, it returns NULL. Also cleanup the workqueue on the error paths. The Linux kernel CVE team has assigned CVE-2025-38171 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit a6a494c8e3ce1fe84aac538b087a4cab868ed83f and fixed in 6.15.3 with commit 7f16be2b2927fdcfe40b596b7411c46d23a82034 Issue introduced in 6.15 with commit a6a494c8e3ce1fe84aac538b087a4cab868ed83f and fixed in 6.16-rc1 with commit 11741b8e382d34b13277497ab91123d8b0b5c2db 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-38171 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/power/supply/max77705_charger.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/7f16be2b2927fdcfe40b596b7411c46d23a82034 https://git.kernel.org/stable/c/11741b8e382d34b13277497ab91123d8b0b5c2db
Powered by blists - more mailing lists