7.5

CVE-2026-53180: linux Improper Locking

CVSS: 7.5v3.1HighModified
AliasesUBUNTU-CVE-2026-53180DEBIAN-CVE-2026-53180CGA-22vq-cjc5-286w
Published 25-06-2026Last modified 19-10-2026

Vulnerability summary

CVE-2026-53180 is a high (CVSS 7.5) Improper Locking vulnerability in linux. EPSS estimates a 0.34% chance of exploitation in the next 30 days, higher than 26% of scored vulnerabilities.

Overall risk
30/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.34%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 19 · Related 19

Timeline

  1. 25-06-2026
    PublishedVulnerability first disclosed.
  2. 19-10-2026
    Last modifiedVulnerability information updated.

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 ]

CVSS metrics

6 scores · 5 sources · 2 versions

EPSS trend

Probability

0.34%

Chance of exploitation in the next 30 days

Percentile

26%

Versus all other CVEs

30-day change

0.00 pp

From 0.34% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.34%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu119 products
  • linuxAll versions (No fix recorded) | < 7.0.0-31.31
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 7.0.0-1012.12
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard12 products
  • linux-aws-6.12< 6.12.95-r0
  • linux-aws-6.18< 6.18.38-r0
  • linux-azure-6.18< 6.18.38-r0
  • linux-gcp-6.12< 6.12.95-r0
  • linux-gcp-6.18< 6.18.38-r0
Linux2 products
  • linux≥ 7ee988770326fca440472200c3eb58935fe712f6, < 07b3b83587fb3012619f4439389b64a955fc7836 | ≥ 7ee988770326fca440472200c3eb58935fe712f6, < 1d6c2062b77be09ec15d6bf637b2e2221c4482fc | ≥ 7ee988770326fca440472200c3eb58935fe712f6, < d338e61ea94052a786aac9f58e9f0d8520afa0fd | ≥ 7ee988770326fca440472200c3eb58935fe712f6, < d486b4934a8e504376b85cdb3766f306d57aff5b | 6.9
  • linux_kernel≥ 6.9, < 6.12.94 | ≥ 6.13, < 6.18.36 | ≥ 6.19, < 7.0.13 | 7.1:rc1 | 7.1:rc2 | 7.1:rc3 | 7.1:rc4 | 7.1:rc5 | 7.1:rc6
Debian1 product
  • linux< 6.12.94-1 | < 7.0.13-1

4 vendors · 134 products

References

22 links
Show all 22 references