CVE-2026-46252: regulator: core: fix locking in regulator_resolve_supply() error path

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-06-03 · updated 2026-07-22
Weakness: CWE-667

Description

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference.

Affected products

Linux kernel: from 4.2.1 before 6.19.4; 4.2, 4.2-rc4, 4.2-rc5, 4.2-rc6, 4.2-rc7, 4.2-rc8 — fixed in 6.19.4

How to fix

Upgrade to a fixed version: Linux kernel 6.19.4. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-46252 or the next vulnerability affects your stack