How severe is CVE-2024-41917?

CVE-2024-41917 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-41917 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-41917?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-41917 have an EU (EUVD) identifier?

Yes. CVE-2024-41917 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-4949.

When was CVE-2024-41917 published?

CVE-2024-41917 was published on 2025-02-12 and last updated on 2026-06-17.

CVE-2024-41917

CVE-2024-41917 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-367.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 5.4
EPSS exploit prediction: 0% (3rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-4949
Weakness: CWE-367
Published: 2025-02-12
Last modified: 2026-06-17

Description

Time-of-check time-of-use race condition for some Intel(R) Battery Life Diagnostic Tool software before version 2.4.1 may allow an authenticated user to potentially enable escalation of privilege via local access.

Frequently asked questions

What is CVE-2024-41917?: Time-of-check time-of-use race condition for some Intel(R) Battery Life Diagnostic Tool software before version 2.4.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
How severe is CVE-2024-41917?: CVE-2024-41917 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-41917 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-41917?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-41917 have an EU (EUVD) identifier?: Yes. CVE-2024-41917 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-4949.
When was CVE-2024-41917 published?: CVE-2024-41917 was published on 2025-02-12 and last updated on 2026-06-17.

References

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01230.html

Other CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) vulnerabilities

CVE-2026-25641 — Critical (CVSS 10.0): SandboxJS is a JavaScript sandboxing library. Prior to 0.8.29, there is a sandbox escape vulnerability due to a…
CVE-2025-64180 — Critical (CVSS 10.0): Manager-io/Manager is accounting software. In Manager Desktop and Server versions 25.11.1.3085 and below, a critical…
CVE-2025-34027 — Critical (CVSS 10.0): The Versa Concerto SD-WAN orchestration platform is vulnerable to an authentication bypass in the Traefik reverse proxy…
CVE-2026-25052 — Critical (CVSS 9.9): n8n is an open source workflow automation platform. Prior to versions 1.123.18 and 2.5.0, a vulnerability in the file…
CVE-2025-13032 — Critical (CVSS 9.9): Double fetch in sandbox kernel driver in Avast/AVG Antivirus <25.3 on windows allows local attacker to escalate…
CVE-2026-53838 — Critical (CVSS 9.8): OpenClaw before 2026.5.27 contains a state mutation vulnerability in node pairing reconnection that allows paired nodes…

Browse all CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) vulnerabilities →