CVE-2024-35983: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: bounds: Use the right number of bits for power-of-two CONFIG_NR_CPUS bits_per() rounds up to the next power of two when passed a power of two. This causes crashes on some machines and configurations.
AI Analysis
Technical Summary
CVE-2024-35983 is a vulnerability identified in the Linux kernel related to the handling of CPU configuration bits, specifically in the function bits_per() which is used to calculate the number of bits required for power-of-two values of CONFIG_NR_CPUS. The issue arises because bits_per() rounds up to the next power of two even when the input is already a power of two, leading to incorrect bit calculations. This miscalculation can cause crashes on certain machines and configurations, likely due to improper memory or resource allocation based on the CPU count. The vulnerability affects multiple Linux kernel versions identified by specific commit hashes, indicating it is present in various recent kernel builds. While no known exploits are currently reported in the wild, the flaw impacts kernel stability and reliability, potentially causing denial of service through system crashes. The root cause is a logic error in kernel code that manages CPU-related configuration parameters, which are critical for system operation and scheduling. The vulnerability has been publicly disclosed and patched, but no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-35983 primarily concerns system stability and availability. Linux is widely used across European enterprises, government agencies, and critical infrastructure for servers, cloud environments, and embedded systems. A kernel crash triggered by this vulnerability could lead to unexpected downtime, service interruptions, and potential data loss if systems are not properly protected or if crashes occur during critical operations. Organizations relying on high-availability Linux systems, such as financial institutions, telecommunications providers, and public sector entities, could face operational disruptions. Although this vulnerability does not directly expose confidentiality or integrity risks, the availability impact can indirectly affect business continuity and service delivery. Additionally, systems with high CPU counts or specific configurations are more susceptible, which may include data centers and HPC clusters common in European research institutions and enterprises.
Mitigation Recommendations
To mitigate CVE-2024-35983, European organizations should promptly apply the official Linux kernel patches that correct the bits_per() function behavior and ensure proper CPU bit calculations. System administrators should verify that their Linux distributions have incorporated these fixes by checking kernel version updates or vendor advisories. For environments where immediate patching is challenging, organizations should consider temporarily reducing CPU configurations to avoid triggering the faulty code path, if feasible. Monitoring system logs for kernel crashes or anomalies related to CPU configuration can help detect attempts to exploit this vulnerability. Additionally, organizations should implement robust backup and recovery procedures to minimize impact from potential crashes. Testing kernel updates in staging environments before production deployment is recommended to ensure compatibility and stability. Finally, maintaining up-to-date hardware firmware and drivers can reduce the risk of crashes caused by kernel miscalculations.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland, Belgium
CVE-2024-35983: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: bounds: Use the right number of bits for power-of-two CONFIG_NR_CPUS bits_per() rounds up to the next power of two when passed a power of two. This causes crashes on some machines and configurations.
AI-Powered Analysis
Technical Analysis
CVE-2024-35983 is a vulnerability identified in the Linux kernel related to the handling of CPU configuration bits, specifically in the function bits_per() which is used to calculate the number of bits required for power-of-two values of CONFIG_NR_CPUS. The issue arises because bits_per() rounds up to the next power of two even when the input is already a power of two, leading to incorrect bit calculations. This miscalculation can cause crashes on certain machines and configurations, likely due to improper memory or resource allocation based on the CPU count. The vulnerability affects multiple Linux kernel versions identified by specific commit hashes, indicating it is present in various recent kernel builds. While no known exploits are currently reported in the wild, the flaw impacts kernel stability and reliability, potentially causing denial of service through system crashes. The root cause is a logic error in kernel code that manages CPU-related configuration parameters, which are critical for system operation and scheduling. The vulnerability has been publicly disclosed and patched, but no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-35983 primarily concerns system stability and availability. Linux is widely used across European enterprises, government agencies, and critical infrastructure for servers, cloud environments, and embedded systems. A kernel crash triggered by this vulnerability could lead to unexpected downtime, service interruptions, and potential data loss if systems are not properly protected or if crashes occur during critical operations. Organizations relying on high-availability Linux systems, such as financial institutions, telecommunications providers, and public sector entities, could face operational disruptions. Although this vulnerability does not directly expose confidentiality or integrity risks, the availability impact can indirectly affect business continuity and service delivery. Additionally, systems with high CPU counts or specific configurations are more susceptible, which may include data centers and HPC clusters common in European research institutions and enterprises.
Mitigation Recommendations
To mitigate CVE-2024-35983, European organizations should promptly apply the official Linux kernel patches that correct the bits_per() function behavior and ensure proper CPU bit calculations. System administrators should verify that their Linux distributions have incorporated these fixes by checking kernel version updates or vendor advisories. For environments where immediate patching is challenging, organizations should consider temporarily reducing CPU configurations to avoid triggering the faulty code path, if feasible. Monitoring system logs for kernel crashes or anomalies related to CPU configuration can help detect attempts to exploit this vulnerability. Additionally, organizations should implement robust backup and recovery procedures to minimize impact from potential crashes. Testing kernel updates in staging environments before production deployment is recommended to ensure compatibility and stability. Finally, maintaining up-to-date hardware firmware and drivers can reduce the risk of crashes caused by kernel miscalculations.
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
- 2024-05-17T13:50:33.145Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9821c4522896dcbddcd5
Added to database: 5/21/2025, 9:08:49 AM
Last enriched: 6/28/2025, 3:27:10 AM
Last updated: 8/15/2025, 10:33:32 AM
Views: 16
Related Threats
CVE-2025-9109: Observable Response Discrepancy in Portabilis i-Diario
MediumCVE-2025-9108: Improper Restriction of Rendered UI Layers in Portabilis i-Diario
MediumCVE-2025-9107: Cross Site Scripting in Portabilis i-Diario
MediumCVE-2025-9106: Cross Site Scripting in Portabilis i-Diario
MediumCVE-2025-9105: Cross Site Scripting in Portabilis i-Diario
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.