PT-2026-46015 · Linux · Linux

Published

2026-06-03

·

Updated

2026-06-03

·

CVE-2026-46252

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.

Related Identifiers

CVE-2026-46252

Affected Products

Linux