← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-53180

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-53180

Key Details

CVECVE-2026-53180
CVSS Score / Version
7.5 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is none; integrity impact is none; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-667 (Improper Locking)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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 ] (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-53180
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-53180
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.