CVE-2026-53180

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 ]

CVSS v3
7.5
EG Score
7.5(high)
EPSS
37.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

timers/migration: Fix livelock in tmigr_handle_remote_up() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d486b4934a8e504376b85cdb3766f306d57aff5b
generic

timers/migration: Fix livelock in tmigr_handle_remote_up() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d338e61ea94052a786aac9f58e9f0d8520afa0fd
generic

timers/migration: Fix livelock in tmigr_handle_remote_up() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d6c2062b77be09ec15d6bf637b2e2221c4482fc
generic

timers/migration: Fix livelock in tmigr_handle_remote_up() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07b3b83587fb3012619f4439389b64a955fc7836

Vendor Advisories for CVE-2026-53180(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 22:01 UTCEG score recompute
  2. 2026-07-06 22:01 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:35 UTCEG score recompute
  6. 2026-07-06 09:35 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 21:09 UTCEG score recompute
  10. 2026-07-05 21:09 UTCGHSA enrichment
  11. 2026-07-05 08:41 UTCEG score recompute
  12. 2026-07-05 08:41 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 20:16 UTCEG score recompute
  16. 2026-07-04 20:15 UTCGHSA enrichment
  17. 2026-07-04 07:50 UTCEG score recompute
  18. 2026-07-04 07:50 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 19:26 UTCEG score recompute
  22. 2026-07-03 19:25 UTCGHSA enrichment
  23. 2026-07-03 07:00 UTCEG score recompute
  24. 2026-07-03 07:00 UTCGHSA enrichment
  25. 2026-07-02 18:25 UTCEG score recompute
Show 21 more
  1. 2026-07-02 18:24 UTCGHSA enrichment
  2. 2026-07-02 05:59 UTCEG score recompute
  3. 2026-07-02 05:59 UTCGHSA enrichment
  4. 2026-07-01 17:34 UTCEG score recompute
  5. 2026-07-01 17:34 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 05:07 UTCEG score recompute▲ 7.50
  8. 2026-07-01 05:07 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  14. 2026-06-28 07:37 UTCEG score recompute
  15. 2026-06-28 07:37 UTCGHSA enrichment
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 10:07 UTCEG score recompute
  21. 2026-06-25 10:07 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53180?
CVE-2026-53180 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: timers/migration: Fix livelock in tmigrhandleremote_up() tmigrhandleremotecpu() skips timerexpire_remote() when cpu == smpprocessorid(), assuming the local softirq path already handled this CPU's timers. This assumption is wrong…
When was CVE-2026-53180 disclosed?
CVE-2026-53180 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53180 actively exploited?
CVE-2026-53180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53180?
CVE-2026-53180 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53180, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53180

Explore →

Is Your Infrastructure Affected by CVE-2026-53180?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs