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 coupling_desc.n_coupled after freeing coupled_rdevs 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 regulator_lock_recursive() due to stale coupling state.
Ensure n_coupled is set to 0 to prevent access to invalid pointers.
Metrics
Affected Vendors & Products
References
History
Thu, 28 Aug 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Sat, 23 Aug 2025 11:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Linux
Linux linux Kernel |
|
Vendors & Products |
Linux
Linux linux Kernel |
Sat, 23 Aug 2025 00:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Fri, 22 Aug 2025 16:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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 coupling_desc.n_coupled after freeing coupled_rdevs 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 regulator_lock_recursive() due to stale coupling state. Ensure n_coupled is set to 0 to prevent access to invalid pointers. | |
Title | regulator: core: fix NULL dereference on unbind due to stale coupling data | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-08-22T16:02:59.680Z
Updated: 2025-08-28T14:44:34.752Z
Reserved: 2025-04-16T04:51:24.031Z
Link: CVE-2025-38668

No data.

Status : Awaiting Analysis
Published: 2025-08-22T16:15:42.283
Modified: 2025-08-28T15:15:58.020
Link: CVE-2025-38668
