In the Linux kernel, the following vulnerability has been resolved: regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK… (CVE-2026-72314)
A vulnerability in the Linux kernel's regulator core was identified where the function regulator_lock_two() incorrectly tests for the error code EDEADLOCK instead of EDEADLK. This causes improper handling of lock contention on certain architectures, notably MIPS, potentially leading to only one of two regulators being locked and triggering a warning. The issue arises because on MIPS, EDEADLK and EDEADLOCK have different values, unlike other architectures where they are the same. This bug does not affect SPARC and PowerPC in practice since the regulator core is not used there.
AI Analysis
Technical Summary
The Linux kernel's regulator_lock_two() function acquires two regulators using nested locking via ww_mutex_lock(), which returns -EDEADLK on contention to signal a retry. However, regulator_lock_two() incorrectly checks for -EDEADLOCK instead of -EDEADLK. On architectures like MIPS where these error codes differ, this causes the function to fail to recognize the deadlock condition properly, resulting in a WARN_ON(ret) and returning with only one regulator locked instead of retrying the lock acquisition. This bug is architecture-specific and primarily affects MIPS platforms where the regulator core is used.
Potential Impact
On affected MIPS systems, this bug can cause improper lock handling in the regulator core, potentially leading to inconsistent locking states where only one regulator is locked instead of both. This could result in unexpected behavior or warnings in kernel operation related to regulator locking. The issue does not affect other architectures in practice due to identical error codes or lack of regulator core usage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users and maintainers of the Linux kernel on MIPS platforms should monitor official Linux kernel updates for a fix addressing this error code comparison issue in regulator_lock_two().
In the Linux kernel, the following vulnerability has been resolved: regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK… (CVE-2026-72314)
Description
A vulnerability in the Linux kernel's regulator core was identified where the function regulator_lock_two() incorrectly tests for the error code EDEADLOCK instead of EDEADLK. This causes improper handling of lock contention on certain architectures, notably MIPS, potentially leading to only one of two regulators being locked and triggering a warning. The issue arises because on MIPS, EDEADLK and EDEADLOCK have different values, unlike other architectures where they are the same. This bug does not affect SPARC and PowerPC in practice since the regulator core is not used there.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's regulator_lock_two() function acquires two regulators using nested locking via ww_mutex_lock(), which returns -EDEADLK on contention to signal a retry. However, regulator_lock_two() incorrectly checks for -EDEADLOCK instead of -EDEADLK. On architectures like MIPS where these error codes differ, this causes the function to fail to recognize the deadlock condition properly, resulting in a WARN_ON(ret) and returning with only one regulator locked instead of retrying the lock acquisition. This bug is architecture-specific and primarily affects MIPS platforms where the regulator core is used.
Potential Impact
On affected MIPS systems, this bug can cause improper lock handling in the regulator core, potentially leading to inconsistent locking states where only one regulator is locked instead of both. This could result in unexpected behavior or warnings in kernel operation related to regulator locking. The issue does not affect other architectures in practice due to identical error codes or lack of regulator core usage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users and maintainers of the Linux kernel on MIPS platforms should monitor official Linux kernel updates for a fix addressing this error code comparison issue in regulator_lock_two().
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g74q-qxv8-58hq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72314"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b71bf8831d5394fbd4b
Added to database: 08/15/2026, 15:53:21 UTC
Last enriched: 08/15/2026, 16:36:40 UTC
Last updated: 08/15/2026, 16:36:40 UTC
Views: 2
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.