CVE-2026-46252

regulator: core: fix locking in regulator_resolve_supply() error path

MEDIUM
5.5
CVSS Score
Published: June 3, 2026 at 03:49 PM UTC
Updated: July 22, 2026 at 08:24 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2 ≤ v < 5.10.2604.2 ≤ v < 5.15.2114.2 ≤ v < 6.1.1774.2 ≤ v < 6.12.954.2 ≤ v < 6.18.374.2 ≤ v < 6.19.44.2 ≤ v < 6.6.1444.2 ≤ v < 7.04.2.1 ≤ v < 6.19.436a1f1b6ddc6d1442424e29548e790633ca39c7b4.24.2 rc44.2 rc54.2 rc64.2 rc74.2 rc8
Vendor states this is fixed in 3b7fffd7a8984a1c009f668765ee7631fd6b87c8 (fixed)
Vendor states this is fixed in 497330b203d2c59c5ff3fa4c34d14494d7203bc3 (fixed)
Vendor states this is fixed in 60747114fd2a38739130b715e7b2d40ce848f0be (fixed)
Vendor states this is fixed in a8a2eab1166bc33ee38ca371cff425bdb5681e47 (fixed)
Vendor states this is fixed in bde74af8d4466213007bdd42cc85fa72c861dea7 (fixed)
Vendor states this is fixed in c66e0db0f37290b53c57994f998bb55590364fd0 (fixed)
Vendor states this is fixed in c84860dac7af7dc3c3e3c9ae86d65e222c2f3b0c (fixed)
Vendor states this is fixed in e77357dc2293283fc08a485b1e2e571d91d02622 (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 5.10.260 (unaffected)
Vendor states this is fixed in 5.15.211 (unaffected)
Vendor states this is fixed in 6.1.177 (unaffected)
Vendor states this is fixed in 6.12.95 (unaffected)
Vendor states this is fixed in 6.18.37 (unaffected)
Vendor states this is fixed in 6.19.4 (unaffected)
Vendor states this is fixed in 6.6.144 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card