CVE-2024-57951: Vulnerability in Linux Linux
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 ]
AI Analysis
Technical Summary
CVE-2024-57951 is a vulnerability in the Linux kernel's high-resolution timer (hrtimers) subsystem related to improper handling of CPU state transitions during CPU hotplug operations. Specifically, when a CPU transitions from an online state (CPUHP_ONLINE) to an intermediate state during hot unplug (CPUHP_HRTIMERS_PREPARE) and then back online, the kernel fails to properly reset certain per-CPU state variables. The function hrtimers_prepare_cpu() does not execute during this transition, leaving cpu_base.hres_active incorrectly set to 1. Concurrently, the tick and clockevent devices are shut down during CPU unplug at CPUHP_AP_TICK_DYING, but upon returning online, the Completely Fair Scheduler (CFS) mistakenly assumes the hrtick is active. This causes the clockevent device to lose the ability to transition to one-shot mode permanently unless the CPU state cycles back to a lower state than CPUHP_HRTIMERS_PREPARE. Additionally, the cpu_base.online flag is not reset to 1 after the transition, triggering warnings (WARN_ON_ONCE) in enqueue_hrtimer(). The stale per-CPU state can lead to dangling pointers, potentially causing kernel instability or crashes. The fix involves adding a startup callback that resets the stale per-CPU state and sets the online flag correctly, ensuring proper CPU state management during hotplug events. This vulnerability affects multiple Linux kernel versions identified by specific commit hashes and was published on February 12, 2025. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions that utilize CPU hotplug functionality, common in high-availability servers, cloud infrastructure, and virtualized environments. Improper CPU state handling can lead to kernel warnings, instability, or crashes, potentially causing denial of service (DoS) conditions. This may disrupt critical services, especially in data centers or cloud platforms heavily reliant on Linux-based systems. While no direct remote code execution or privilege escalation is indicated, the instability could be exploited by local attackers or malicious processes to degrade system reliability. Given the widespread use of Linux in European enterprises, telecommunications, and government infrastructure, the vulnerability could impact service continuity and operational resilience. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to accidental or targeted disruption. Organizations with dynamic CPU management or those employing CPU hotplug for power management or maintenance are particularly at risk.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernels to versions that include the patch addressing CVE-2024-57951. Since the vulnerability relates to CPU hotplug handling, administrators should audit systems that use CPU hotplug features, especially in virtualized or containerized environments. Specific mitigation steps include: 1) Applying vendor-provided kernel updates or patches promptly; 2) Testing kernel updates in staging environments to ensure compatibility with CPU hotplug operations; 3) Monitoring kernel logs for WARN_ON_ONCE messages related to hrtimers or CPU state transitions as indicators of potential exploitation or instability; 4) Limiting CPU hotplug usage where feasible until patches are applied; 5) Employing kernel hardening and integrity monitoring tools to detect anomalous behavior; 6) Ensuring backup and recovery procedures are robust to mitigate potential service disruptions caused by kernel instability. Additionally, organizations should maintain close communication with Linux distribution vendors for timely security advisories and patches.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-57951: Vulnerability in Linux Linux
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 ]
AI-Powered Analysis
Technical Analysis
CVE-2024-57951 is a vulnerability in the Linux kernel's high-resolution timer (hrtimers) subsystem related to improper handling of CPU state transitions during CPU hotplug operations. Specifically, when a CPU transitions from an online state (CPUHP_ONLINE) to an intermediate state during hot unplug (CPUHP_HRTIMERS_PREPARE) and then back online, the kernel fails to properly reset certain per-CPU state variables. The function hrtimers_prepare_cpu() does not execute during this transition, leaving cpu_base.hres_active incorrectly set to 1. Concurrently, the tick and clockevent devices are shut down during CPU unplug at CPUHP_AP_TICK_DYING, but upon returning online, the Completely Fair Scheduler (CFS) mistakenly assumes the hrtick is active. This causes the clockevent device to lose the ability to transition to one-shot mode permanently unless the CPU state cycles back to a lower state than CPUHP_HRTIMERS_PREPARE. Additionally, the cpu_base.online flag is not reset to 1 after the transition, triggering warnings (WARN_ON_ONCE) in enqueue_hrtimer(). The stale per-CPU state can lead to dangling pointers, potentially causing kernel instability or crashes. The fix involves adding a startup callback that resets the stale per-CPU state and sets the online flag correctly, ensuring proper CPU state management during hotplug events. This vulnerability affects multiple Linux kernel versions identified by specific commit hashes and was published on February 12, 2025. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions that utilize CPU hotplug functionality, common in high-availability servers, cloud infrastructure, and virtualized environments. Improper CPU state handling can lead to kernel warnings, instability, or crashes, potentially causing denial of service (DoS) conditions. This may disrupt critical services, especially in data centers or cloud platforms heavily reliant on Linux-based systems. While no direct remote code execution or privilege escalation is indicated, the instability could be exploited by local attackers or malicious processes to degrade system reliability. Given the widespread use of Linux in European enterprises, telecommunications, and government infrastructure, the vulnerability could impact service continuity and operational resilience. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to accidental or targeted disruption. Organizations with dynamic CPU management or those employing CPU hotplug for power management or maintenance are particularly at risk.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernels to versions that include the patch addressing CVE-2024-57951. Since the vulnerability relates to CPU hotplug handling, administrators should audit systems that use CPU hotplug features, especially in virtualized or containerized environments. Specific mitigation steps include: 1) Applying vendor-provided kernel updates or patches promptly; 2) Testing kernel updates in staging environments to ensure compatibility with CPU hotplug operations; 3) Monitoring kernel logs for WARN_ON_ONCE messages related to hrtimers or CPU state transitions as indicators of potential exploitation or instability; 4) Limiting CPU hotplug usage where feasible until patches are applied; 5) Employing kernel hardening and integrity monitoring tools to detect anomalous behavior; 6) Ensuring backup and recovery procedures are robust to mitigate potential service disruptions caused by kernel instability. Additionally, organizations should maintain close communication with Linux distribution vendors for timely security advisories and patches.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-01-19T11:50:08.381Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9820c4522896dcbdd216
Added to database: 5/21/2025, 9:08:48 AM
Last enriched: 6/27/2025, 10:57:28 PM
Last updated: 8/11/2025, 11:43:25 AM
Views: 15
Related Threats
CVE-2025-8895: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in cozmoslabs WP Webhooks – Automate repetitive tasks by creating powerful automation workflows directly within WordPress
CriticalCVE-2025-7390: CWE-295 Improper Certificate Validation in Softing Industrial Automation GmbH OPC UA C++ SDK
CriticalCVE-2025-53505: Improper limitation of a pathname to a restricted directory ('Path Traversal') in Intermesh BV Group-Office
MediumCVE-2025-53504: Cross-site scripting (XSS) in Intermesh BV Group-Office
MediumCVE-2025-48355: CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere in ProveSource LTD ProveSource Social Proof
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.