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

High 7.8 Published Updated

Incorrect deadlock detection in Linux kernel regulator code causes lock inconsistency on MIPS, potentially leading to system instability or denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-72314?

CVE-2026-72314 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Which versions are affected by CVE-2026-72314?

How do I fix CVE-2026-72314?

Apply the vendor's patch.

Is CVE-2026-72314 being exploited?

There is no known exploitation of CVE-2026-72314 in the wild and no public exploit code.

Sources

Also known as BELL-CVE-2026-72314, DEBIAN-CVE-2026-72314, GHSA-g74q-qxv8-58hq, UBUNTU-CVE-2026-72314.

Is CVE-2026-72314 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free