Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-21813

kernel: timers/migration: Fix off-by-one root mis-connection

Overview

Published
27 Feb 2025
Modified
17 Jun 2026
Medium CVE
0 Registry packages
42 OS packages
5 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-193

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Oracle Linux 1 release · 1 package

fixed 1
kernel-uek
Oracle Linux fixes for CVE-2025-21813
ReleasePackageFixed in
9 kernel-uek +34 6.12.0-102.36.5.2.el9uek

debian 2 releases · 1 package

fixed 2
linux
debian fixes for CVE-2025-21813
ReleasePackageFixed in
13 linux 6.12.15-1
14 linux 6.12.15-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2025-21813
ReleasePackageFixed in
linux 6.12.15-1

root.io debian 1 release · 1 package

fixed 1
rootio-linux
root.io debian fixes for CVE-2025-21813
ReleasePackageFixed in
13 rootio-linux 6.12.15-1

ubuntu 1 release · 4 packages

fixed 4
linux-lowlatency-hwe-6-11 linux-azure-6-11 linux-oem-6-11 linux-hwe-6-11
ubuntu fixes for CVE-2025-21813
ReleasePackageFixed in
24.04 linux-lowlatency-hwe-6-11 6.11.0-1013.14~24.04.1
24.04 linux-azure-6-11 +1 6.11.0-1014.14~24.04.1
24.04 linux-oem-6-11 6.11.0-1021.21
24.04 linux-hwe-6-11 6.11.0-25.25~24.04.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.