CVE-2025-40116 json
usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup
published 2025-11-12 11 mo ago modified 2026-10-19 20 d ago also EUVD-2025-124967
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3, 6.18
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.17.6-1
debian advisories DEBIAN-CVE-2025-40116
- linux Ubuntu 22.04 LTS 5.15.0-170.180
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 22.04 LTS 5.15.0-1100.107
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1100.109
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
ubuntu advisories UBUNTU-CVE-2025-40116
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1.21.15
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
- kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.61.1
- kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.61.1
suse advisories SUSE-SU-2026:20473-1SUSE-SU-2026:20496-1SUSE-SU-2026:20039-1SUSE-SU-2026:20059-1SUSE-SU-2025:4521-1SUSE-SU-2025:4517-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.8.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.8.1
- kernel-kvmsmall openSUSE Leap 16.0 6.12.0-160000.8.1
opensuse advisories openSUSE-SU-2025:20172-1
- git.kernel.org/stable/c/89838fe5c6c010ff8d3924f22afd9c18c5c95310 commit
- git.kernel.org/stable/c/3facf69a735e730ae36387f18780fe420708aa91 commit
- git.kernel.org/stable/c/e0e0ce06f3571be9b26790e4df56ba37b1de8543 commit
- git.kernel.org/stable/c/3723c3dda1cc82c9bbca08fcbd46705a361bfd56 commit
- git.kernel.org/stable/c/b0439e3762ac9ea580f714e1504a1827d1ad32f5 commit
- git.kernel.org/stable/c/e68ea6de1d0551f90d7a2c75f82cb3ebe5e397dc commit
- git.kernel.org/stable/c/b682ce44bf20ada752a2f6ce70d5a575c56f6a35 commit
- git.kernel.org/stable/c/186e8f2bdba551f3ae23396caccd452d985c23e3 commit
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/89838fe5c6c010ff8d3924f22afd9c18c5c95310
- git.kernel.org /stable/c/3facf69a735e730ae36387f18780fe420708aa91
- git.kernel.org /stable/c/e0e0ce06f3571be9b26790e4df56ba37b1de8543
- git.kernel.org /stable/c/3723c3dda1cc82c9bbca08fcbd46705a361bfd56
- git.kernel.org /stable/c/b0439e3762ac9ea580f714e1504a1827d1ad32f5
- git.kernel.org /stable/c/e68ea6de1d0551f90d7a2c75f82cb3ebe5e397dc
- git.kernel.org /stable/c/b682ce44bf20ada752a2f6ce70d5a575c56f6a35
- git.kernel.org /stable/c/186e8f2bdba551f3ae23396caccd452d985c23e3
Sources
- CVE List CVE-2025-40116
- NVD CVE-2025-40116
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.