CVE-2024-35985: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: sched/eevdf: Prevent vlag from going out of bounds in reweight_eevdf() It was possible to have pick_eevdf() return NULL, which then causes a NULL-deref. This turned out to be due to entity_eligible() returning falsely negative because of a s64 multiplcation overflow. Specifically, reweight_eevdf() computes the vlag without considering the limit placed upon vlag as update_entity_lag() does, and then the scaling multiplication (remember that weight is 20bit fixed point) can overflow. This then leads to the new vruntime being weird which then causes the above entity_eligible() to go side-ways and claim nothing is eligible. Thus limit the range of vlag accordingly. All this was quite rare, but fatal when it does happen.
AI Analysis
Technical Summary
CVE-2024-35985 is a vulnerability identified in the Linux kernel's scheduler component, specifically within the eevdf (Earliest Eligible Virtual Deadline First) scheduling class. The flaw arises in the function reweight_eevdf(), which is responsible for recalculating the scheduling weight (vlag) of entities (tasks or processes) in the scheduler. The vulnerability is due to a failure to properly limit the vlag value during computation, leading to a potential 64-bit signed integer multiplication overflow. This overflow causes the vruntime (virtual runtime) to be incorrectly calculated, which in turn causes the entity_eligible() function to return a false negative. As a result, the pick_eevdf() function may return NULL, leading to a NULL pointer dereference and subsequent kernel crash (kernel panic). This is a rare but fatal bug that can cause denial of service by crashing the Linux kernel. The root cause is the lack of bounds checking on vlag in reweight_eevdf(), unlike in update_entity_lag(), which properly limits vlag. The fix involves constraining vlag within safe limits to prevent overflow and ensure correct eligibility checks. This vulnerability affects Linux kernel versions identified by specific commits (hashes provided), and no known exploits are currently reported in the wild. The issue is critical because it impacts the core kernel scheduler, which is fundamental to system stability and process management.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in environments running vulnerable Linux kernel versions, especially in servers, cloud infrastructure, and embedded systems relying on the eevdf scheduler. A successful exploitation leads to a kernel crash, causing denial of service and potential disruption of critical services. This can impact availability of business-critical applications, cloud services, and network infrastructure. Organizations in sectors such as finance, healthcare, telecommunications, and government, which heavily depend on Linux-based systems, could face operational downtime and associated financial and reputational damage. Additionally, while no remote code execution or privilege escalation is indicated, the denial of service could be leveraged as part of a broader attack chain or to disrupt incident response activities. The rarity of the bug and the requirement for specific kernel versions limit the scope, but the severity of impact on system availability is significant.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Identify and inventory Linux systems running affected kernel versions by checking kernel commit hashes or version numbers corresponding to the vulnerability. 2) Apply the official Linux kernel patches that address CVE-2024-35985 as soon as they become available from trusted sources such as the Linux kernel mailing list or vendor security advisories. 3) For systems where immediate patching is not feasible, consider temporarily disabling or avoiding the use of the eevdf scheduler if possible, or use alternative scheduling classes until patched. 4) Monitor system logs and kernel crash reports for signs of NULL pointer dereferences or unexpected kernel panics related to scheduling. 5) Implement robust kernel crash recovery mechanisms and maintain up-to-date backups to minimize downtime impact. 6) Engage with Linux distribution vendors for backported patches and security updates tailored to their supported kernel versions. 7) Incorporate this vulnerability into vulnerability management and incident response plans to ensure timely detection and remediation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2024-35985: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: sched/eevdf: Prevent vlag from going out of bounds in reweight_eevdf() It was possible to have pick_eevdf() return NULL, which then causes a NULL-deref. This turned out to be due to entity_eligible() returning falsely negative because of a s64 multiplcation overflow. Specifically, reweight_eevdf() computes the vlag without considering the limit placed upon vlag as update_entity_lag() does, and then the scaling multiplication (remember that weight is 20bit fixed point) can overflow. This then leads to the new vruntime being weird which then causes the above entity_eligible() to go side-ways and claim nothing is eligible. Thus limit the range of vlag accordingly. All this was quite rare, but fatal when it does happen.
AI-Powered Analysis
Technical Analysis
CVE-2024-35985 is a vulnerability identified in the Linux kernel's scheduler component, specifically within the eevdf (Earliest Eligible Virtual Deadline First) scheduling class. The flaw arises in the function reweight_eevdf(), which is responsible for recalculating the scheduling weight (vlag) of entities (tasks or processes) in the scheduler. The vulnerability is due to a failure to properly limit the vlag value during computation, leading to a potential 64-bit signed integer multiplication overflow. This overflow causes the vruntime (virtual runtime) to be incorrectly calculated, which in turn causes the entity_eligible() function to return a false negative. As a result, the pick_eevdf() function may return NULL, leading to a NULL pointer dereference and subsequent kernel crash (kernel panic). This is a rare but fatal bug that can cause denial of service by crashing the Linux kernel. The root cause is the lack of bounds checking on vlag in reweight_eevdf(), unlike in update_entity_lag(), which properly limits vlag. The fix involves constraining vlag within safe limits to prevent overflow and ensure correct eligibility checks. This vulnerability affects Linux kernel versions identified by specific commits (hashes provided), and no known exploits are currently reported in the wild. The issue is critical because it impacts the core kernel scheduler, which is fundamental to system stability and process management.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in environments running vulnerable Linux kernel versions, especially in servers, cloud infrastructure, and embedded systems relying on the eevdf scheduler. A successful exploitation leads to a kernel crash, causing denial of service and potential disruption of critical services. This can impact availability of business-critical applications, cloud services, and network infrastructure. Organizations in sectors such as finance, healthcare, telecommunications, and government, which heavily depend on Linux-based systems, could face operational downtime and associated financial and reputational damage. Additionally, while no remote code execution or privilege escalation is indicated, the denial of service could be leveraged as part of a broader attack chain or to disrupt incident response activities. The rarity of the bug and the requirement for specific kernel versions limit the scope, but the severity of impact on system availability is significant.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Identify and inventory Linux systems running affected kernel versions by checking kernel commit hashes or version numbers corresponding to the vulnerability. 2) Apply the official Linux kernel patches that address CVE-2024-35985 as soon as they become available from trusted sources such as the Linux kernel mailing list or vendor security advisories. 3) For systems where immediate patching is not feasible, consider temporarily disabling or avoiding the use of the eevdf scheduler if possible, or use alternative scheduling classes until patched. 4) Monitor system logs and kernel crash reports for signs of NULL pointer dereferences or unexpected kernel panics related to scheduling. 5) Implement robust kernel crash recovery mechanisms and maintain up-to-date backups to minimize downtime impact. 6) Engage with Linux distribution vendors for backported patches and security updates tailored to their supported kernel versions. 7) Incorporate this vulnerability into vulnerability management and incident response plans to ensure timely detection and remediation.
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
- 2024-05-17T13:50:33.145Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9828c4522896dcbe2387
Added to database: 5/21/2025, 9:08:56 AM
Last enriched: 6/29/2025, 8:56:26 AM
Last updated: 7/31/2025, 10:33:54 AM
Views: 16
Related Threats
CVE-2025-7384: CWE-502 Deserialization of Untrusted Data in crmperks Database for Contact Form 7, WPforms, Elementor forms
CriticalCVE-2025-8491: CWE-352 Cross-Site Request Forgery (CSRF) in nikelschubert Easy restaurant menu manager
MediumCVE-2025-0818: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ninjateam File Manager Pro – Filester
MediumCVE-2025-8901: Out of bounds write in Google Chrome
HighCVE-2025-8882: Use after free in Google Chrome
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.