CVE-2024-57951hrtimers: Handle CPU state correctly on hotplug

Description

In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ]

Timeline

Scores

EPSS (exploitation in 30 days)

0.27% · top 81% of all CVEs (13 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: total

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

Affected products

• Linux · Linux

  • affected 54d0d83a53508d687fd4a225f8aa1f18559562d0 – < 95e4f62df23f4df1ce6ef897d44b8e23c260921a
  • affected 7f4c89400d2997939f6971c7981cc780a219e36b – < 14984139f1f2768883332965db566ef26db609e7
  • affected 6fcbcc6c8e52650749692c7613cbe71bf601670d – < 15b453db41d36184cf0ccc21e7df624014ab6a1a
  • affected 75b5016ce325f1ef9c63e5398a1064cf8a7a7354 – < 3d41dbf82e10c44e53ea602398ab002baec27e75
  • affected 53f408cad05bb987af860af22f4151e5a18e6ee8 – < a5cbbea145b400e40540c34816d16d36e0374fbc
  • affected 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 – < 38492f6ee883c7b1d33338bf531a62cff69b4b28
  • affected 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 – < 2f8dea1692eef2b7ba6a256246ed82c365fdc686
  • affected 9a2fc41acb69dd4e2a58d0c04346c3333c2341fc
  • affected 5.4.264 – < 5.4.290
  • affected 5.10.204 – < 5.10.234
  • affected 5.15.143 – < 5.15.177
  • affected 6.1.68 – < 6.1.127
  • affected 6.6.7 – < 6.6.74
  • affected 4.19.302 – < 4.20

• Linux · Linux

  • affected 6.7
  • unaffected < 6.7
  • unaffected 5.4.290 – ≤ 5.4.*
  • unaffected 5.10.234 – ≤ 5.10.*
  • unaffected 5.15.177 – ≤ 5.15.*
  • unaffected 6.1.127 – ≤ 6.1.*
  • unaffected 6.6.74 – ≤ 6.6.*
  • unaffected 6.12.11 – ≤ 6.12.*
  • unaffected 6.13 – ≤ *

Sources

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

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2024-53854 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

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

Record last updated 15 Oct 2026, 01:01 UTC.