VulnerabilityPublished 12 Aug 2025Updated 13 Aug 2025

CVE-2025-24515: Intel(R) Graphics Drivers · Denial of Service

Affects Intel(R) Graphics DriversSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-24515, European organizations should take several specific steps beyond generic advice: 1) Inventory and identify all systems using affected Intel Graphics Drivers, prioritizing those in critical operational roles or multi-user environments. 2) Monitor Intel's official channels for patches or driver updates addressing this vulnerability and apply them promptly once available. 3) Restrict local access to systems with affected drivers to trusted users only, employing strict access controls and user account management to reduce the risk of exploitation by unauthorized or low-privilege users. 4) Implement endpoint detection and response (EDR) solutions to monitor for unusual system crashes or driver failures that could indicate exploitation attempts. 5) For environments using shared workstations or VDI, consider isolating user sessions and limiting the ability of users to execute code or commands that could trigger the vulnerability. 6) Educate users about the risks of local exploits and encourage reporting of system instability or crashes. 7) As a temporary workaround, if feasible, consider disabling or rolling back to a previous stable version of the Intel Graphics Driver until a patch is released, balancing this against potential loss of functionality or performance.

Description

NULL pointer dereference for some Intel(R) Graphics Drivers may allow an authenticated user to potentially enable denial of service via local access.

Impact

For European organizations, the impact of CVE-2025-24515 could be significant in environments relying on Intel integrated graphics hardware, which is common in corporate desktops and laptops. The denial of service caused by the driver crash can disrupt normal business operations, especially in sectors where graphical user interface availability is critical, such as design, engineering, finance, and administrative functions. This disruption could lead to productivity losses and potentially impact service delivery if critical systems become unresponsive. Although the vulnerability does not directly compromise data confidentiality or integrity, the availability impact could be leveraged as part of a broader attack chain to cause operational disruption. In multi-user or shared workstation environments, such as call centers or public access terminals, the risk is elevated because an authenticated user could intentionally or accidentally trigger the DoS. Additionally, organizations with remote desktop or virtual desktop infrastructure (VDI) setups using Intel graphics may experience service interruptions. The lack of known exploits in the wild reduces immediate risk, but the medium severity rating and local access requirement mean that internal threat actors or attackers who have gained initial access could exploit this vulnerability to cause denial of service.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01299.html (opens in a new tab)

Community reviews

Loading reviews…