diff options
| author | Alessandro Carminati <acarmina@redhat.com> | 2025-06-26 08:38:09 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-08-01 09:47:28 +0100 |
| commit | 233d3c54c9620e95193923859ea1d0b0f5d748ca (patch) | |
| tree | 86057cf2f994c91e1bad86de9b978e1929f8cd30 /drivers/regulator | |
| parent | 0e8c65939ba2aab32b3ea7c2e9037ec3327241b3 (diff) | |
| download | linux-233d3c54c9620e95193923859ea1d0b0f5d748ca.tar.gz linux-233d3c54c9620e95193923859ea1d0b0f5d748ca.tar.bz2 linux-233d3c54c9620e95193923859ea1d0b0f5d748ca.zip | |
regulator: core: fix NULL dereference on unbind due to stale coupling data
[ Upstream commit ca46946a482238b0cdea459fb82fc837fb36260e ]
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.
Signed-off-by: Alessandro Carminati <acarmina@redhat.com>
Link: https://patch.msgid.link/20250626083809.314842-1-acarmina@redhat.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/regulator')
| -rw-r--r-- | drivers/regulator/core.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index d2e21dc61dd7..1d49612eeb7e 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -5422,6 +5422,7 @@ static void regulator_remove_coupling(struct regulator_dev *rdev) ERR_PTR(err)); } + rdev->coupling_desc.n_coupled = 0; kfree(rdev->coupling_desc.coupled_rdevs); rdev->coupling_desc.coupled_rdevs = NULL; } |