cbcvebase.
CVE-2024-57951
published 2025-02-12

CVE-2024-57951: In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions…

PriorityP337high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.23%
14.3th percentile
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 ]

Affected

36 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.128-1 (bookworm)linux 6.1.128-1 (bookworm)
debianlinux-6.1< linux 6.1.128-1 (bookworm)linux 6.1.128-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux>= 4.19.302 < 4.204.20
linuxlinux>= 5.10.204 < 5.10.2345.10.234
linuxlinux>= 5.15.143 < 5.15.1775.15.177
linuxlinux>= 5.4.264 < 5.4.2905.4.290
linuxlinux>= 53f408cad05bb987af860af22f4151e5a18e6ee8 < a5cbbea145b400e40540c34816d16d36e0374fbca5cbbea145b400e40540c34816d16d36e0374fbc
linuxlinux>= 54d0d83a53508d687fd4a225f8aa1f18559562d0 < 95e4f62df23f4df1ce6ef897d44b8e23c260921a95e4f62df23f4df1ce6ef897d44b8e23c260921a
linuxlinux>= 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 < 38492f6ee883c7b1d33338bf531a62cff69b4b2838492f6ee883c7b1d33338bf531a62cff69b4b28
linuxlinux>= 5c0930ccaad5a74d74e8b18b648c5eb21ed2fe94 < 2f8dea1692eef2b7ba6a256246ed82c365fdc6862f8dea1692eef2b7ba6a256246ed82c365fdc686
linuxlinux>= 6.1.68 < 6.1.1276.1.127
linuxlinux>= 6.6.7 < 6.6.746.6.74
linuxlinux>= 6fcbcc6c8e52650749692c7613cbe71bf601670d < 15b453db41d36184cf0ccc21e7df624014ab6a1a15b453db41d36184cf0ccc21e7df624014ab6a1a
linuxlinux>= 75b5016ce325f1ef9c63e5398a1064cf8a7a7354 < 3d41dbf82e10c44e53ea602398ab002baec27e753d41dbf82e10c44e53ea602398ab002baec27e75
linuxlinux>= 7f4c89400d2997939f6971c7981cc780a219e36b < 14984139f1f2768883332965db566ef26db609e714984139f1f2768883332965db566ef26db609e7
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.128-16.1.128-1
linuxlinux_kernel>= 0 < 6.12.11-16.12.11-1
linuxlinux_kernel>= 0 < 6.12.11-16.12.11-1
linuxlinux_kernel>= 0 < 5.4.0-211.2315.4.0-211.231
linuxlinux_kernel>= 0 < 5.15.0-135.1465.15.0-135.146
linuxlinux_kernel>= 0 < 6.8.0-62.656.8.0-62.65

CVSS provenance

nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_msrc7.8HIGH
vendor_redhat7.8HIGH
vendor_ubuntu7.8HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.