CVE-2025-21816 Details
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.
A vulnerability exists in the Linux kernel's hrtimer management during CPU hotplug operations. When a CPU is marked as dying, hrtimers should be migrated to an online CPU to avoid disrupting bandwidth timer tasks. However, the outgoing CPU can still perform wakeups that rearm bandwidth timers, potentially leading to them being directed to an offline CPU, where they are ignored. This issue affects the RCU subsystem and the stop machine kthread, which can inadvertently arm timers from an offline CPU, causing them to be mismanaged. The vulnerability arises because the hrtimer infrastructure does not consistently migrate timers from offline to online CPUs, especially when timers are enqueued from a dying CPU.
The vulnerability has been addressed by modifying the hrtimer infrastructure to ensure that timers are always migrated to an online CPU whenever they are enqueued from an offline CPU. This change allows for the removal of previous workarounds implemented for the RCU subsystem.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.19.302, < 4.20 >= 5.4.264, < 5.5 >= 5.10.204, < 5.11 >= 5.15.143, < 5.16 >= 6.1.68, < 6.1.141 >= 6.6.7, < 6.6.93 >= 6.7.1, < 6.12.14 >= 6.13, < 6.13.3 6.7 - 6.7 rc2 6.7 rc3 6.7 rc4 6.7 rc5 6.7 rc6 6.7 rc7 6.7 rc8 6.14 rc1 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 3, 2025 | CVE Modified | CVE |
| Oct 28, 2025 | Initial Analysis | [email protected] |
| Jun 4, 2025 | CVE Modified | kernel.org |
| Feb 27, 2025 | New CVE Received | kernel.org |