Answer in brief
CVE-2024-57951 records a High severity (CVSS 7.8) vulnerability in hrtimers: Handle CPU state correctly on hotplug. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=54d0d83a53508d687fd4a225f8aa1f18559562d0 <95e4f62df23f4df1ce6ef897d44b8e23c260921a || >=7f4c89400d2997939f6971c7981cc780a219e36b <14984139f1f2768883332965db566ef26db609e7 || >=6fcbcc6c8e52650749692c7613cbe71bf601670d <15b453db41d36184cf0ccc21e7df624014ab6a1a || >=75b5016ce325f1ef9c63e5398a1064cf8a7a7354 <3d41dbf82e10c44e53ea602398ab002baec27e75 || >=53f408cad05bb987af860af22f4151e5a18e6ee8 <a5cbbea145b400e40540c34816d16d36e0374fbc || >=5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 <38492f6ee883c7b1d33338bf531a62cff69b4b28 || >=5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 <2f8dea1692eef2b7ba6a256246ed82c365fdc686 || 9a2fc41acb69dd4e2a58d0c04346c3333c2341fc || >=5.4.264 <5.4.290 || >=5.10.204 <5.10.234 || >=5.15.143 <5.15.177 || >=6.1.68 <6.1.127 || >=6.6.7 <6.6.74 || >=4.19.302 <4.20 | 95e4f62df23f4df1ce6ef897d44b8e23c260921a, 14984139f1f2768883332965db566ef26db609e7, 15b453db41d36184cf0ccc21e7df624014ab6a1a, 3d41dbf82e10c44e53ea602398ab002baec27e75, a5cbbea145b400e40540c34816d16d36e0374fbc, 38492f6ee883c7b1d33338bf531a62cff69b4b28, 2f8dea1692eef2b7ba6a256246ed82c365fdc686, 5.4.290, 5.10.234, 5.15.177, 6.1.127, 6.6.74, 4.20 |
| Linux/Linuxgeneric | 6.7 | Not reported |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.2 | V3.2 |
| Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 familygeneric | >=0 <V3.2 | V3.2 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.2 | V3.2 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <V1.1.1 | V1.1.1 |
Published upstream
Feb 12, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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 ]
Quoted source text, attributed separately from HOL analysis.