Answer in brief
CVE-2026-53180 records a High severity (CVSS 7.5) vulnerability in timers/migration: Fix livelock in tmigr_handle_remote_up(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7ee988770326fca440472200c3eb58935fe712f6 <07b3b83587fb3012619f4439389b64a955fc7836 || >=7ee988770326fca440472200c3eb58935fe712f6 <1d6c2062b77be09ec15d6bf637b2e2221c4482fc || >=7ee988770326fca440472200c3eb58935fe712f6 <d338e61ea94052a786aac9f58e9f0d8520afa0fd || >=7ee988770326fca440472200c3eb58935fe712f6 <d486b4934a8e504376b85cdb3766f306d57aff5b | 07b3b83587fb3012619f4439389b64a955fc7836, 1d6c2062b77be09ec15d6bf637b2e2221c4482fc, d338e61ea94052a786aac9f58e9f0d8520afa0fd, d486b4934a8e504376b85cdb3766f306d57aff5b |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-53180 records a High severity (CVSS 7.5) vulnerability in timers/migration: Fix livelock in tmigr_handle_remote_up(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7ee988770326fca440472200c3eb58935fe712f6 <07b3b83587fb3012619f4439389b64a955fc7836 || >=7ee988770326fca440472200c3eb58935fe712f6 <1d6c2062b77be09ec15d6bf637b2e2221c4482fc || >=7ee988770326fca440472200c3eb58935fe712f6 <d338e61ea94052a786aac9f58e9f0d8520afa0fd || >=7ee988770326fca440472200c3eb58935fe712f6 <d486b4934a8e504376b85cdb3766f306d57aff5b | 07b3b83587fb3012619f4439389b64a955fc7836, 1d6c2062b77be09ec15d6bf637b2e2221c4482fc, d338e61ea94052a786aac9f58e9f0d8520afa0fd, d486b4934a8e504376b85cdb3766f306d57aff5b |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.