Linux: Improper Locking
CVE-2026-53054 is a high-severity improper locking vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 206f812ef140727b75697111391ae320fd8aa652, d9ecf758270501b2e7a0bc1dd69a6f28f1ae3cae, 85042c2cd970a6b0e686329387096fe19989ae62 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.13% 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 206f812ef140727b75697111391ae320fd8aa652 or d9ecf758270501b2e7a0bc1dd69a6f28f1ae3cae or 85042c2cd970a6b0e686329387096fe19989ae62, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.18.33 or 7.0.10, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 2e6a8a1fe2b262a6dfd0a65041fcd830ee1e7143 up to, but not including, 206f812ef140727b75697111391ae320fd8aa652; 2e6a8a1fe2b262a6dfd0a65041fcd830ee1e7143 up to, but not including, d9ecf758270501b2e7a0bc1dd69a6f28f1ae3cae; 2e6a8a1fe2b262a6dfd0a65041fcd830ee1e7143 up to, but not including, 85042c2cd970a6b0e686329387096fe19989ae62; 6.17 | 206f812ef140727b75697111391ae320fd8aa652, d9ecf758270501b2e7a0bc1dd69a6f28f1ae3cae, 85042c2cd970a6b0e686329387096fe19989ae62 |
| Linux | Linux Kernel | 6.17 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10 | 6.18.33, 7.0.10 |
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
- LocalThe attacker needs local access or must trick a user into running something.
- 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:L/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: drm/msm: Fix VM_BIND UNMAP locking Wrong argument meant that the objs involved in UNMAP ops were not always getting locked. Since _NO_SHARE objs share a common resv with the VM (which is always locked) this would only show up with non-_NO_SHARE BOs. Patchwork: https://patchwork.freedesktop.org/patch/713898/
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Improper Locking vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.