CVE-2026-46252: regulator: core: fix locking in regulator_resolve_supply() error path
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3b7fffd7a8984a1c009f668765ee7631fd6b87c8, 497330b203d2c59c5ff3fa4c34d14494d7203bc3, 60747114fd2a38739130b715e7b2d40ce848f0be.
Low priority for now. Upgrade to Linux Linux 3b7fffd7a8984a1c009f668765ee7631fd6b87c8, 497330b203d2c59c5ff3fa4c34d14494d7203bc3, 60747114fd2a38739130b715e7b2d40ce848f0be or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 3, 2026
- Updated
- Jul 22, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.2.1 and later · before 6.19.4
- linux linux kernel4.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.2affected
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before e77357dc2293283fc08a485b1e2e571d91d02622affected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before a8a2eab1166bc33ee38ca371cff425bdb5681e47affected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before 60747114fd2a38739130b715e7b2d40ce848f0beaffected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before c84860dac7af7dc3c3e3c9ae86d65e222c2f3b0caffected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before 3b7fffd7a8984a1c009f668765ee7631fd6b87c8affected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before bde74af8d4466213007bdd42cc85fa72c861dea7affected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before c66e0db0f37290b53c57994f998bb55590364fd0affected · git
- 36a1f1b6ddc6d1442424e29548e790633ca39c7b and later · before 497330b203d2c59c5ff3fa4c34d14494d7203bc3affected · git
- before 4.2not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.177-1 | 6.1.177-1 |
| Debian:13 | linux | before 6.12.95-1 | 6.12.95-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46250Jun 3, 2026 · MIPS: Work around LLVM bug when gp is used as global register variable29Monitor
- ← EarlierCVE-2026-46251Jun 3, 2026 · btrfs: fix block_group_tree dirty_list corruption33Monitor
- Later →CVE-2026-46255Jun 3, 2026 · dmaengine: fsl-edma: don't explicitly disable clocks in .remove()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3b7fffd7a8984a1c009f668765ee7631fd6b87c8 | Vendor (CNA) |
| Linux Linux | 497330b203d2c59c5ff3fa4c34d14494d7203bc3 | Vendor (CNA) |
| Linux Linux | 60747114fd2a38739130b715e7b2d40ce848f0be | Vendor (CNA) |
| Linux Linux | a8a2eab1166bc33ee38ca371cff425bdb5681e47 | Vendor (CNA) |
| Linux Linux | bde74af8d4466213007bdd42cc85fa72c861dea7 | Vendor (CNA) |
| Linux Linux | c66e0db0f37290b53c57994f998bb55590364fd0 | Vendor (CNA) |
| Linux Linux | c84860dac7af7dc3c3e3c9ae86d65e222c2f3b0c | Vendor (CNA) |
| Linux Linux | e77357dc2293283fc08a485b1e2e571d91d02622 | Vendor (CNA) |
| debian:linux | 6.1.177-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/497330b203d2c59c5ff3fa4c34d14494d7203bc3
- git.kernel.org/stable/c/60747114fd2a38739130b715e7b2d40ce848f0be
- git.kernel.org/stable/c/a8a2eab1166bc33ee38ca371cff425bdb5681e47
- git.kernel.org/stable/c/bde74af8d4466213007bdd42cc85fa72c861dea7
- git.kernel.org/stable/c/c66e0db0f37290b53c57994f998bb55590364fd0
- git.kernel.org/stable/c/c84860dac7af7dc3c3e3c9ae86d65e222c2f3b0c
- git.kernel.org/stable/c/e77357dc2293283fc08a485b1e2e571d91d02622
Vendor advisories and official records. Exploit/PoC links are deliberately left out.