Linux Kernel up to 6.19.3 regulator drivers/regulator/core.c regulator_resolve_supply locking

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.3 and classified as critical. This vulnerability affects the function regulator_resolve_supply of the file drivers/regulator/core.c of the component regulator. Such manipulation leads to locking. This vulnerability is uniquely identified as CVE-2026-46252. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.3. It has been rated as critical. Affected by this issue is the function regulator_resolve_supply of the file drivers/regulator/core.c of the component regulator. The manipulation with an unknown input leads to a locking vulnerability. Using CWE to declare the problem leads to CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. Impacted is availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-46252 since 05/13/2026. The exploitation is known to be difficult. Technical details are known, but there is no available exploit.

Upgrading to version 6.19.4 eliminates this vulnerability. Applying the patch c66e0db0f37290b53c57994f998bb55590364fd0/497330b203d2c59c5ff3fa4c34d14494d7203bc3 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.19.0
• 6.19.1
• 6.19.2
• 6.19.3

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion