CVE-2026-46252
MediumCVSS 5.5Exploitation Probability (EPSS)
Low risk1th percentile - higher than 1% of all known CVEs
Summary
In the Linux kernel, a locking issue was found in the error path of regulator_resolve_supply() in the voltage regulator driver. When late enabling of a supply regulator fails, the code calls _regulator_put() without holding the regulator_list_mutex, triggering a lockdep warning. The fix switches to regulator_put() and adds proper locking to prevent concurrent access to rdev while clearing the supply pointer.
Risk Assessment
The organization may experience system instability or false lockdep warnings when working with voltage regulators, complicating diagnostics and potentially leading to unexpected kernel behavior.
Recommendation
It is recommended to immediately update the Linux kernel to a version containing this fix to avoid lockdep warnings and potential synchronization issues in the regulator error path.
Original NVD description (English source)
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.