CVE-2026-53180
Last modified
CVE-2026-53180 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.47% chance of exploitation in the next 30 days.
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 ]
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.9, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53180?
How severe is CVE-2026-53180?
How do I fix CVE-2026-53180?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53175In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53176In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53177In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53178In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-53179In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-5318A weakness has been identified in LibRaw up to 0.22.0. This …4.3
- CVE-2026-53181In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53182In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53183In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53184In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53185In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53186In the Linux kernel, the following vulnerability has been re…9.1
Are you affected by CVE-2026-53180?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
