# CVE-2026-46252: regulator: core: fix locking in regulator_resolve_supply() error path

> A locking error in the Linux kernel regulator core can cause a lockdep warning and potential system instability during supply resolution failures.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jun 2026
- **Updated:** 4 Jul 2026
- **Also known as:** AZL-89354, BELL-CVE-2026-46252, DEBIAN-CVE-2026-46252, GHSA-w447-hxj8-xq6p, ROOT-OS-DEBIAN-11-CVE-2026-46252, ROOT-OS-DEBIAN-12-CVE-2026-46252, ROOT-OS-DEBIAN-13-CVE-2026-46252, ROOT-OS-UBUNTU-2204-CVE-2026-46252, ROOT-OS-UBUNTU-2404-CVE-2026-46252, UBUNTU-CVE-2026-46252

## What is CVE-2026-46252?

CVE-2026-46252 is a medium-severity vulnerability in Linux kernel, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2026-46252?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46252?

Apply the vendor's patch.

## Is CVE-2026-46252 being exploited?

There is no known exploitation of CVE-2026-46252 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46252 and fix it if it is affected.

What it is: CVE-2026-46252 is a medium-severity vulnerability in Linux kernel, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46252 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46252/ (Markdown: https://insights.sbomify.com/CVE-2026-46252/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46252
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46252
- OSV: https://osv.dev/vulnerability/CVE-2026-46252

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46252/
Summaries are generated and may contain mistakes; the official description above is the record.