regulator: core: fix NULL dereference on unbind due to stale coupling data
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d8ca7d184b33af7913c244900df77c6cad6a5590 · < 5d4261dbb3335221fd9c6e69f909ba79ee6663a7| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel regulator core can retain stale coupling data after a regulator is unbound. If regulator operations access that data afterward, a NULL pointer dereference can cause a kernel panic. The input does not specify whether an attacker can trigger these conditions or what access would be required.
Teams running the Linux kernel should check whether their kernel includes the regulator core fix; affected versions were not provided.