CVE-2025-32739: Intel(R) Graphics Drivers and Intel LTS kernels · Denial of Service
Affects Intel(R) Graphics Drivers and Intel LTS kernelsSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Intel(R) Graphics Drivers and Intel LTS kernels | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-32739, organizations should: 1) Monitor Intel’s security advisories closely and apply firmware and driver updates as soon as patches become available. 2) Restrict local access to systems running vulnerable Intel graphics drivers and LTS kernels, enforcing strict user authentication and least privilege principles. 3) Implement robust endpoint security controls to detect and prevent unauthorized local access or privilege escalation attempts. 4) Conduct regular audits of user accounts and session activity to identify suspicious behavior that could precede exploitation. 5) Use system monitoring tools to detect abnormal system crashes or instability that may indicate exploitation attempts. 6) In environments with critical uptime requirements, consider deploying redundancy or failover mechanisms to minimize the impact of potential DoS conditions. 7) Engage with Intel support or security teams for guidance on affected versions and patch timelines once available.
Description
Improper conditions check in some firmware for some Intel(R) Graphics Drivers and Intel LTS kernels within Ring 1: Device Drivers may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.