Linux: Improper Locking
CVE-2026-53180 is a high-severity improper locking vulnerability in Linux, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 07b3b83587fb3012619f4439389b64a955fc7836, 1d6c2062b77be09ec15d6bf637b2e2221c4482fc, d338e61ea94052a786aac9f58e9f0d8520afa0fd 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.34% 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 07b3b83587fb3012619f4439389b64a955fc7836 or 1d6c2062b77be09ec15d6bf637b2e2221c4482fc or d338e61ea94052a786aac9f58e9f0d8520afa0fd or d486b4934a8e504376b85cdb3766f306d57aff5b, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.94 or 6.18.36 or 7.0.13, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 7ee988770326fca440472200c3eb58935fe712f6 up to, but not including, 07b3b83587fb3012619f4439389b64a955fc7836; 7ee988770326fca440472200c3eb58935fe712f6 up to, but not including, 1d6c2062b77be09ec15d6bf637b2e2221c4482fc; 7ee988770326fca440472200c3eb58935fe712f6 up to, but not including, d338e61ea94052a786aac9f58e9f0d8520afa0fd; 7ee988770326fca440472200c3eb58935fe712f6 up to, but not including, d486b4934a8e504376b85cdb3766f306d57aff5b; 6.9 | 07b3b83587fb3012619f4439389b64a955fc7836, 1d6c2062b77be09ec15d6bf637b2e2221c4482fc, d338e61ea94052a786aac9f58e9f0d8520afa0fd, d486b4934a8e504376b85cdb3766f306d57aff5b |
| Linux | Linux Kernel | 6.9 up to, but not including, 6.12.94; 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.1 | 6.12.94, 6.18.36, 7.0.13 |
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
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: timers/migration: Fix livelock in tmigr_handle_remote_up() tmigr_handle_remote_cpu() skips timer_expire_remote() when cpu == smp_processor_id(), assuming the local softirq path already handled this CPU's timers. This assumption is wrong because jiffies can advance after the handling of the CPU's global timers in run_timer_base(BASE_GLOBAL) and before tmigr_handle_remote() evaluates the expiry times. As a consequence a timer which expires after the CPU local timer wheel advanced and becomes expired in the remote handling is ignored and the callback is never invoked and removed from the timer wheel. What's worse is that fetch_next_timer_interrupt_remote() keeps reporting it as expired, and the event is re-queued with expires == now on each iteration. The goto-again loop spins indefinitely. Fix this by calling timer_expire_remote() unconditionally. That's minimal overhead for the common case as __run_timer_base() returns immediately if there is nothing to expire in the local wheel. [ tglx: Amend change log and add a comment ]
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: yes, technical impact: partial).
- 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
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.