CVE-2026-72314
Vulnérabilité élevée dans Linux (Linux)
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.
Gravité et risque d'exploitation
CVE-2026-72314 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 6.7 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions 5.10.180, <=6.1.*, <29a7953e9adea6c7f9e64947745b79158e7cea7f, 5224ea575196db11c0a909a78ea426ccdb92f064, 6.2.15, <=6.12.*, 6.18.40, 7.1.5, 5.15.111, <5.15.212, 0, 1e3056b8067c2e9b7741c4e588f0acacbe4bdafc, cba6cfdc7c3f1516f0d08ddfb24e689af0932573, 435c65af581a61ca249bd8f717c3a147dc119f11, <=7.1.*, 6.4, 849ab4cf182b38e562ffcc1b494d510e948822dd, <8e39aa63798ea0a797fd9341419f12ef91df3238, <6.3, <0c305eac40470a224671858a215963b070f9b2a9, 6.1.178, <=5.10.*, <=6.6.*, cdc042430ea9e07f77ce05a9d29e227dbdecc733, 6.12.97, <6.1.178, <d38f8bd771c4999b797d7074b348cf201414bd34, <6.4, 06140d6dfe720d80566f792b4e28a9cd60a67970, <5.5, <=6.18.*, 5.15.212, 6.6.145, 5.10.261, <e2063307ea3b6da74585129ba7b588e8243e2ef0, <5.10.261, <346e2d666a29ae7233c56b356a0487eb1d42589b, 6.1.28, <=*, <dc804f390fddd9c389edf0976356942e16878d8f, <=5.15.*, <153d1b8b5bc30847eb70ad535f62f289aa9217e6, 5.4.243, 7.2, 6.3.2) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- 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
