CVE-2025-38668: regulator: core: fix NULL dereference on unbind due to stale coupling data
In the Linux kernel, the following vulnerability has been resolved:
regulator: core: fix NULL dereference on unbind due to stale coupling data
Failing to reset couplingdesc.ncoupled after freeing coupledrdevs can lead to NULL pointer dereference when regulators are accessed post-unbind.
This can happen during runtime PM or other regulator operations that rely on coupling metadata.
For example, on ridesx4, unbinding the 'reg-dummy' platform device triggers a panic in regulatorlockrecursive() due to stale coupling state.
Ensure ncoupled is set to 0 to prevent access to invalid pointers.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38668?
CVE-2025-38668 has a moderate severity level due to the potential for a NULL pointer dereference.
How do I fix CVE-2025-38668?
The fix for CVE-2025-38668 is to update to the latest version of the Linux kernel that includes the patch.
Which versions of the Linux kernel are affected by CVE-2025-38668?
CVE-2025-38668 affects various versions of the Linux kernel where the NULL dereference issue has not been addressed.
What causes the CVE-2025-38668 vulnerability?
CVE-2025-38668 is caused by failing to reset the coupling_desc.n_coupled after freeing coupled_rdevs.
Can CVE-2025-38668 lead to system crashes?
Yes, if exploited, CVE-2025-38668 can lead to system instability or crashes due to a NULL pointer dereference.