https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 20:48:51 +0000 https://vulnerability.circl.lu/vuln/cve-2026-46252 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>regulator: core: fix locking in regulator_resolve_supply() error path</p> <p>If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning:</p> <p>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</p> <p>as the regulator_list_mutex must be held when calling _regulator_put().</p> <p>To solve this, simply switch to using regulator_put().</p> <p>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.</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>regulator: core: fix locking in regulator_resolve_supply() error path</p> <p>If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning:</p> <p>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</p> <p>as the regulator_list_mutex must be held when calling _regulator_put().</p> <p>To solve this, simply switch to using regulator_put().</p> <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-46252