Linux: Improper Locking
CVE-2026-72100 is a high-severity improper locking vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions f7989286175f32db8605e767a1a2efc62e894dc8, aa5113e7155f4ea81d2c0303ab5cb272d4b32627, 3d1afaa074622859678b1a1e7c1b9c0af74c89b0 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to f7989286175f32db8605e767a1a2efc62e894dc8 or aa5113e7155f4ea81d2c0303ab5cb272d4b32627 or 3d1afaa074622859678b1a1e7c1b9c0af74c89b0 or 5a266764fadaff8b5c1fe37a186ebf9b09cb953e, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | fb0987682c629c1d2c476f35f6fde405a5e304a4 up to, but not including, f7989286175f32db8605e767a1a2efc62e894dc8; fb0987682c629c1d2c476f35f6fde405a5e304a4 up to, but not including, aa5113e7155f4ea81d2c0303ab5cb272d4b32627; fb0987682c629c1d2c476f35f6fde405a5e304a4 up to, but not including, 3d1afaa074622859678b1a1e7c1b9c0af74c89b0; fb0987682c629c1d2c476f35f6fde405a5e304a4 up to, but not including, 5a266764fadaff8b5c1fe37a186ebf9b09cb953e; 6.11 | f7989286175f32db8605e767a1a2efc62e894dc8, aa5113e7155f4ea81d2c0303ab5cb272d4b32627, 3d1afaa074622859678b1a1e7c1b9c0af74c89b0, 5a266764fadaff8b5c1fe37a186ebf9b09cb953e |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix a bug if the bio is out of limits If dm_integrity_check_limits fails, the code would exit with DM_MAPIO_KILL. However, the range would be already locked at this point, and it wouldn't be unlocked, resulting in a deadlock. Let's move the limit check up, so that when it exits, no resources are leaked.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Locking
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
How developers prevent this class of flaw
- Use industry standard APIs to implement locking mechanism.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Improper Locking vulnerabilities
- 7.8 High severity
- 8.0 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 7.8 High severity
Spotted an error? Tell us.