Kernel crash via error-pointer cleanup dereference
Published Nov 12, 2025 · Updated Nov 12, 2025
Invalid-pointer dereference in Linux 3.16 through affected stable branches allows attackers to crash the kernel during MAX3421 probe failure. In max3421_probe(), kthread_run() can return an error pointer, but cleanup passes spi_thread to kthread_stop() after checking only for NULL. The path requires the MAX3421 host-controller driver to probe and thread creation or later initialization to fail; the bounded consequence is a kernel crash rather than code execution.
Summary
What happened
Invalid-pointer dereference in Linux 3.16 through affected stable branches allows attackers to crash the kernel during MAX3421 probe failure. In max3421_probe(), kthread_run() can return an error pointer, but cleanup passes spi_thread to kthread_stop() after checking only for NULL. The path requires the MAX3421 host-controller driver to probe and thread creation or later initialization to fail; the bounded consequence is a kernel crash rather than code execution.
The record
- CVE
- CVE-2025-40116
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <186e8f2bdba551f3ae23396caccd452d985c23e3
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <3723c3dda1cc82c9bbca08fcbd46705a361bfd56
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <3facf69a735e730ae36387f18780fe420708aa91
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <89838fe5c6c010ff8d3924f22afd9c18c5c95310
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <b0439e3762ac9ea580f714e1504a1827d1ad32f5
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <b682ce44bf20ada752a2f6ce70d5a575c56f6a35
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <e0e0ce06f3571be9b26790e4df56ba37b1de8543
- Affected versionversion=05dfa5c9bc37933181b619e42ec0eeb41ef31362 <e68ea6de1d0551f90d7a2c75f82cb3ebe5e397dc
- Affected versionversion=3.16
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo