PT-2026-52276 · Linux · Linux
Published
2026-06-25
·
Updated
2026-06-25
·
CVE-2026-53180
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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 ]
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux