| 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: <2025111251-CVE-2025-40116-3942@gregkh> Date: Wed, 12 Nov 2025 19:23:52 +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-40116: usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup The kthread_run() function returns error pointers so the max3421_hcd->spi_thread pointer can be either error pointers or NULL. Check for both before dereferencing it. The Linux kernel CVE team has assigned CVE-2025-40116 to this issue. Affected and fixed versions =========================== Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 5.4.301 with commit 89838fe5c6c010ff8d3924f22afd9c18c5c95310 Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 5.10.246 with commit 3facf69a735e730ae36387f18780fe420708aa91 Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 5.15.195 with commit e0e0ce06f3571be9b26790e4df56ba37b1de8543 Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 6.1.156 with commit 3723c3dda1cc82c9bbca08fcbd46705a361bfd56 Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 6.6.112 with commit b0439e3762ac9ea580f714e1504a1827d1ad32f5 Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 6.12.53 with commit e68ea6de1d0551f90d7a2c75f82cb3ebe5e397dc Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 6.17.3 with commit b682ce44bf20ada752a2f6ce70d5a575c56f6a35 Issue introduced in 3.16 with commit 05dfa5c9bc37933181b619e42ec0eeb41ef31362 and fixed in 6.18-rc1 with commit 186e8f2bdba551f3ae23396caccd452d985c23e3 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-40116 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/usb/host/max3421-hcd.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/89838fe5c6c010ff8d3924f22afd9c18c5c95310 https://git.kernel.org/stable/c/3facf69a735e730ae36387f18780fe420708aa91 https://git.kernel.org/stable/c/e0e0ce06f3571be9b26790e4df56ba37b1de8543 https://git.kernel.org/stable/c/3723c3dda1cc82c9bbca08fcbd46705a361bfd56 https://git.kernel.org/stable/c/b0439e3762ac9ea580f714e1504a1827d1ad32f5 https://git.kernel.org/stable/c/e68ea6de1d0551f90d7a2c75f82cb3ebe5e397dc https://git.kernel.org/stable/c/b682ce44bf20ada752a2f6ce70d5a575c56f6a35 https://git.kernel.org/stable/c/186e8f2bdba551f3ae23396caccd452d985c23e3
Powered by blists - more mailing lists