High 7.8Published Aug 15, 2026

CVE-2026-72314regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK

Updated under an hour ago (Oct 28, 2026, 4:30 AM ET)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK Compare against -EDEADLK, which is what ww_mutex_lock() actually returns and what every other deadlock check in this file already uses. Function regulator_lock_two() acquires two regulators via regulator_lock_nested() -> ww_mutex_lock(). On contention, ww_mutex_lock() returns -EDEADLK, which is the caller's signal to drop the lock it holds and retry the acquisition in the canonical order. However, regulator_lock_two() tests the return value against -EDEADLOCK rather than -EDEADLK. On most architectures, EDEADLK and EDEADLOCK are the same value, so the comparison happens to be correct and the bug is invisible. But on MIPS, SPARC, and PowerPC, those two errors have different values. The test is wrong: a genuine -EDEADLK backoff no longer matches -EDEADLOCK, so instead of unlocking and retrying, the code falls into WARN_ON(ret) and returns with only one of the two regulators locked. In practice, this is a bug only on MIPS, because the regulator core is not built or used on the other two platforms. In general, EDEADLK is preferred over EDEADLOCK for new code.

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Received
Record last updated: Oct 16, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 06140d6dfe720d80566f792b4e28a9cd60a67970 before dc804f390fddd9c389edf0976356942e16878d8f; from 1e3056b8067c2e9b7741c4e588f0acacbe4bdafc before 8e39aa63798ea0a797fd9341419f12ef91df3238; 849ab4cf182b38e562ffcc1b494d510e948822dd builds before 0c305eac40470a224671858a215963b070f9b2a9; from cba6cfdc7c3f1516f0d08ddfb24e689af0932573 before 29a7953e9adea6c7f9e64947745b79158e7cea7f; from cba6cfdc7c3f1516f0d08ddfb24e689af0932573 before e2063307ea3b6da74585129ba7b588e8243e2ef0; from cba6cfdc7c3f1516f0d08ddfb24e689af0932573 before 346e2d666a29ae7233c56b356a0487eb1d42589b; from cba6cfdc7c3f1516f0d08ddfb24e689af0932573 before 153d1b8b5bc30847eb70ad535f62f289aa9217e6; from cba6cfdc7c3f1516f0d08ddfb24e689af0932573 before d38f8bd771c4999b797d7074b348cf201414bd34; and 9 more ranges	CNA record

References

References

https://git.kernel.org/stable/c/dc804f390fddd9c389edf0976356942e16878d8f
https://git.kernel.org/stable/c/8e39aa63798ea0a797fd9341419f12ef91df3238
https://git.kernel.org/stable/c/0c305eac40470a224671858a215963b070f9b2a9
https://git.kernel.org/stable/c/29a7953e9adea6c7f9e64947745b79158e7cea7f
https://git.kernel.org/stable/c/e2063307ea3b6da74585129ba7b588e8243e2ef0
https://git.kernel.org/stable/c/346e2d666a29ae7233c56b356a0487eb1d42589b
https://git.kernel.org/stable/c/153d1b8b5bc30847eb70ad535f62f289aa9217e6
https://git.kernel.org/stable/c/d38f8bd771c4999b797d7074b348cf201414bd34

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.