regulator: core: fix locking in regulator_resolve_supply() error path
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle
AI Analysis
Technical Summary
The Linux kernel contained a vulnerability in the regulator core subsystem where, if late enabling of a supply regulator failed in regulator_resolve_supply(), the code triggered a lockdep warning due to improper locking. Specifically, the regulator_list_mutex was not held when calling _regulator_put(), violating locking requirements. The fix replaced _regulator_put() with regulator_put() and added locking to prevent concurrent access to the regulator device (rdev) while clearing the supply pointer. This correction prevents potential race conditions and ensures proper locking discipline in the error path. The vulnerable code is planned for removal in a future commit, but the fix was applied beforehand for stability and reference.
Potential Impact
This vulnerability does not affect confidentiality or integrity but impacts availability by causing potential denial of service through kernel warnings and possible deadlocks or race conditions in the regulator subsystem. There are no known exploits in the wild. The issue is limited to local attackers with low privileges due to the local attack vector and requires user-level privileges to trigger.
Mitigation Recommendations
No official patch links are provided in the data, but the vulnerability has been resolved in the Linux kernel source by replacing unsafe locking calls and adding proper locking mechanisms. Users should update to the latest Linux kernel versions that include this fix once available. Since this is not a cloud service, remediation depends on applying kernel updates from the vendor or distribution. Patch status is not yet confirmed in this data; check the vendor advisory for current remediation guidance.
regulator: core: fix locking in regulator_resolve_supply() error path
Description
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle
CVSS v3.1
Score 5.5medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a vulnerability in the regulator core subsystem where, if late enabling of a supply regulator failed in regulator_resolve_supply(), the code triggered a lockdep warning due to improper locking. Specifically, the regulator_list_mutex was not held when calling _regulator_put(), violating locking requirements. The fix replaced _regulator_put() with regulator_put() and added locking to prevent concurrent access to the regulator device (rdev) while clearing the supply pointer. This correction prevents potential race conditions and ensures proper locking discipline in the error path. The vulnerable code is planned for removal in a future commit, but the fix was applied beforehand for stability and reference.
Potential Impact
This vulnerability does not affect confidentiality or integrity but impacts availability by causing potential denial of service through kernel warnings and possible deadlocks or race conditions in the regulator subsystem. There are no known exploits in the wild. The issue is limited to local attackers with low privileges due to the local attack vector and requires user-level privileges to trigger.
Mitigation Recommendations
No official patch links are provided in the data, but the vulnerability has been resolved in the Linux kernel source by replacing unsafe locking calls and adding proper locking mechanisms. Users should update to the latest Linux kernel versions that include this fix once available. Since this is not a cloud service, remediation depends on applying kernel updates from the vendor or distribution. Patch status is not yet confirmed in this data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w447-hxj8-xq6p
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-46252"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a498a7827e9c7971936efd6
Added to database: 07/04/2026, 22:34:32 UTC
Last enriched: 07/04/2026, 23:07:23 UTC
Last updated: 07/31/2026, 19:24:47 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.