Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21816hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING

Description

In the Linux kernel, the following vulnerability has been resolved: hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING hrtimers are migrated away from the dying CPU to any online target at the CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers handling tasks involved in the CPU hotplug forward progress. However wakeups can still be performed by the outgoing CPU after CPUHP_AP_HRTIMERS_DYING. Those can result again in bandwidth timers being armed. Depending on several considerations (crystal ball power management based election, earliest timer already enqueued, timer migration enabled or not), the target may eventually be the current CPU even if offline. If that happens, the timer is eventually ignored. The most notable example is RCU which had to deal with each and every of those wake-ups by deferring them to an online CPU, along with related workarounds: _ e787644caf76 (rcu: Defer RCU kthreads wakeup when CPU is dying) _ 9139f93209d1 (rcu/nocb: Fix RT throttling hrtimer armed from offline CPU) _ f7345ccc62a4 (rcu/nocb: Fix rcuog wake-up from offline softirq) The problem isn't confined to RCU though as the stop machine kthread (which runs CPUHP_AP_HRTIMERS_DYING) reports its completion at the end of its work through cpu_stop_signal_done() and performs a wake up that eventually arms the deadline server timer: WARNING: CPU: 94 PID: 588 at kernel/time/hrtimer.c:1086 hrtimer_start_range_ns+0x289/0x2d0 CPU: 94 UID: 0 PID: 588 Comm: migration/94 Not tainted Stopper: multi_cpu_stop+0x0/0x120 <- stop_machine_cpuslocked+0x66/0xc0 RIP: 0010:hrtimer_start_range_ns+0x289/0x2d0 Call Trace: <TASK> start_dl_timer enqueue_dl_entity dl_server_start enqueue_task_fair enqueue_task ttwu_do_activate try_to_wake_up complete cpu_stopper_thread Instead of providing yet another bandaid to work around the situation, fix it in the hrtimers infrastructure instead: always migrate away a timer to an online target whenever it is enqueued from an offline CPU. This will also allow to revert all the above RCU disgraceful hacks.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21816, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 75b5016ce325f1ef9c63e5398a1064cf8a7a7354 – < 82ac6adbbb2aad14548a71d5e2e37f4964a15e38
    • affected 53f408cad05bb987af860af22f4151e5a18e6ee8 – < 63815bef47ec25f5a125019ca480882481ee1553
    • affected 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 – < e456a88bddae4030ba962447bb84be6669f2a0c1
    • affected 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 – < 2aecec58e9040ce3d2694707889f9914a2374955
    • affected 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 – < 53dac345395c0d2493cbc2f4c85fe38aef5b63f5
    • affected 9a2fc41acb69dd4e2a58d0c04346c3333c2341fc
    • affected 54d0d83a53508d687fd4a225f8aa1f18559562d0
    • affected 7f4c89400d2997939f6971c7981cc780a219e36b
    • affected 6fcbcc6c8e52650749692c7613cbe71bf601670d
    • affected 6.1.68 – < 6.1.141
    • affected 6.6.7 – < 6.6.93
    • affected 4.19.302 – < 4.20
    • affected 5.4.264 – < 5.5
    • affected 5.10.204 – < 5.11
    • affected 5.15.143 – < 5.16
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.1.141 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.14 – ≤ 6.12.*
    • unaffected 6.13.3 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21816 badge
[![CVE-2025-21816](https://cveledger.app/badge/CVE-2025-21816.svg)](https://cveledger.app/cve/CVE-2025-21816)

Record last updated .