CVE-2025-21813 Details
Description
In the Linux kernel, the following vulnerability has been resolved: timers/migration: Fix off-by-one root mis-connection Before attaching a new root to the old root, the children counter of the new root is checked to verify that only the upcoming CPU's top group have been connected to it. However since the recently added commit b729cc1ec21a ("timers/migration: Fix another race between hotplug and idle entry/exit") this check is not valid anymore because the old root is pre-accounted as a child to the new root. Therefore after connecting the upcoming CPU's top group to the new root, the children count to be expected must be 2 and not 1 anymore. This omission results in the old root to not be connected to the new root. Then eventually the system may run with more than one top level, which defeats the purpose of a single idle migrator. Also the old root is pre-accounted but not connected upon the new root creation. But it can be connected to the new root later on. Therefore the old root may be accounted twice to the new root. The propagation of such overcommit can end up creating a double final top-level root with a groupmask incorrectly initialized. Although harmless given that the final top level roots will never have a parent to walk up to, this oddity opportunistically reported the core issue: WARNING: CPU: 8 PID: 0 at kernel/time/timer_migration.c:543 tmigr_requires_handle_remote CPU: 8 UID: 0 PID: 0 Comm: swapper/8 RIP: 0010:tmigr_requires_handle_remote Call Trace: <IRQ> ? tmigr_requires_handle_remote ? hrtimer_run_queues update_process_times tick_periodic tick_handle_periodic __sysvec_apic_timer_interrupt sysvec_apic_timer_interrupt </IRQ> Fix the problem by taking the old root into account in the children count of the new root so the connection is not omitted. Also warn when more than one top level group exists to better detect similar issues in the future.
An off-by-one vulnerability has been identified in the Linux kernel's timer migration handling. This issue arises during the process of connecting a new root to an old one, where the children counter of the new root is supposed to verify that only the upcoming CPU's top group has been linked. However, a recent commit introduced a race condition that invalidates this check, allowing the old root to remain improperly connected. As a result, the system may operate with multiple top-level groups, undermining the intended single idle migrator structure. Additionally, the old root can be accounted twice to the new root, leading to an incorrectly initialized group mask. While this double accounting is not harmful in itself, it highlights the core issue, which can cause system warnings about improper timer migration handling.
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.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/6f449d8fa1808a7f9ee644866bbc079285dbefdd | kernel.org | Patch |
| https://git.kernel.org/stable/c/868c9037df626b3c245ee26a290a03ae1f9f58d3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c6dd70e5b465a2b77c7a7c3d868736d302e29aec | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-193 | Off-by-one Error | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12.11, < 6.12.14 >= 6.13.1, < 6.13.3 6.13 - 6.14 rc1 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 28, 2025 | Initial Analysis | [email protected] |
| Feb 27, 2025 | New CVE Received | kernel.org |