Improper Locking Affecting torvalds/linux package, versions [5.10.180,5.10.261)[5.15.111,5.15.212)[6.1.28,6.1.178)[5.4.243,5.5)[6.2.15,6.3)[6.3.2,6.4)[6.4,6.6.145)[6.7,6.12.97)[6.13,6.18.40)[6.19,7.1.5)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-UNMANAGED-TORVALDSLINUX-20794700
- published11 Oct 2026
- disclosed15 Aug 2026
- creditUnknown
Introduced: 15 Aug 2026
CVE-2026-72314 (opens in a new tab)How to fix?
Upgrade torvalds/linux to version 5.10.261, 5.15.212, 6.1.178, 5.5, 6.3, 6.4, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or higher.
Overview
Affected versions of this package are vulnerable to Improper Locking in the regulator_lock_two process. An attacker can cause kernel memory disclosure, heap/list corruption, use-after-free conditions, or arbitrary kernel writes by triggering concurrent regulator supply resolution during driver probing on affected architectures, leading to inconsistent locking states and potential kernel deadlocks or system hangs. This is only exploitable if the system is running on MIPS architecture, as the regulator core is not built or used on other affected platforms.
Note: The Linux kernel project assigns a CVE to every bug fix it ships, whether or not the bug has been shown to be exploitable. This advisory was generated from that process and has not been individually assessed for exploitability. See the kernel's CVE process documentation: https://github.com/torvalds/linux/blob/master/Documentation/process/cve.rst