CVE-2025-40296: platform/x86: int3472: Fix double free of GPIO device during unregister
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: int3472: Fix double free of GPIO device during unregister
regulatorunregister() already frees the associated GPIO device. On ThinkPad X9 (Lunar Lake), this causes a double free issue that leads to random failures when other drivers (typically Intel THC) attempt to allocate interrupts. The root cause is that the reference count of the pinctrlintelplatform module unexpectedly drops to zero when this driver defers its probe.
This behavior can also be reproduced by unloading the module directly.
Fix the issue by removing the redundant release of the GPIO device during regulator unregistration.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In the Linux kernel platform/x86 int3472 driver, remove the redundant release of the GPIO device during unregister; regulator_unregister() already frees the associated GPIO device.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-40296?
CVE-2025-40296 is classified as a medium severity vulnerability due to the potential for a double free issue leading to memory corruption.
How do I fix CVE-2025-40296?
To fix CVE-2025-40296, update the Linux kernel to the latest version where the vulnerability has been patched.
What software is affected by CVE-2025-40296?
CVE-2025-40296 affects the Linux kernel, particularly on platforms utilizing the int3472 driver.
What is the impact of CVE-2025-40296?
The impact of CVE-2025-40296 includes potential system crashes or arbitrary code execution due to memory management issues.
Who discovered CVE-2025-40296?
CVE-2025-40296 was identified during code audits and testing of the Linux kernel.