CVE-2025-21816

hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING

State
Published
Severity
Not scored
Published
Feb 27, 2025
Updated
May 23, 2026
Reserved
Dec 29, 2024

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 75b5016ce325f1ef9c63e5398a1064cf8a7a7354 to before 82ac6adbbb2aad14548a71d5e2e37f4964a15e38Affected
  • 53f408cad05bb987af860af22f4151e5a18e6ee8 to before 63815bef47ec25f5a125019ca480882481ee1553Affected
  • 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 to before e456a88bddae4030ba962447bb84be6669f2a0c1Affected
  • 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 to before 2aecec58e9040ce3d2694707889f9914a2374955Affected
  • 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 to before 53dac345395c0d2493cbc2f4c85fe38aef5b63f5Affected
  • 9a2fc41acb69dd4e2a58d0c04346c3333c2341fcAffected
  • 54d0d83a53508d687fd4a225f8aa1f18559562d0Affected
  • 7f4c89400d2997939f6971c7981cc780a219e36bAffected
  • 6fcbcc6c8e52650749692c7613cbe71bf601670dAffected
  • 6.1.68 to before 6.1.141Affected
  • 6.6.7 to before 6.6.93Affected
  • 4.19.302 to before 4.20Affected
  • 5.4.264 to before 5.5Affected
  • 5.10.204 to before 5.11Affected
  • 5.15.143 to before 5.16Affected
LinuxLinux
  • 6.7Affected
  • before 6.7Not affected
  • 6.1.141 through 6.1.*Not affected
  • 6.6.93 through 6.6.*Not affected
  • 6.12.14 through 6.12.*Not affected
  • 6.13.3 through 6.13.*Not affected
  • 6.14 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.