# CVE-2025-32739: Denial of service in Intel(R) Graphics Drivers and Intel LTS kernels

> An unprivileged local attacker can cause a denial of service in Intel Graphics Drivers and LTS kernels via improper condition checks.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-ggrw-x635-4pj7

## What is CVE-2025-32739?

CVE-2025-32739 is a low-severity denial of service vulnerability in Intel Graphics Driver, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2025-32739?

It affects 3 products.


Products: Intel Graphics Driver, Intel Graphics Software, Intel Linux Intel Lts Kernel.

## How do I fix CVE-2025-32739?

No fix has been published for CVE-2025-32739 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32739 being exploited?

There is no known exploitation of CVE-2025-32739 in the wild and no public exploit code.

## Other vulnerabilities in Intel Graphics Driver

- [CVE-2018-12214](https://insights.sbomify.com/CVE-2018-12214/): Memory corruption in Intel(R) Graphics Driver for Windows (high 8.2)
- [CVE-2018-12216](https://insights.sbomify.com/CVE-2018-12216/): Code injection in Intel(R) Graphics Driver for Windows (high 8.2)
- [CVE-2018-12220](https://insights.sbomify.com/CVE-2018-12220/): Privilege escalation in Intel(R) Graphics Driver for Windows (high 8.2)
- [CVE-2020-0504](https://insights.sbomify.com/CVE-2020-0504/): Memory corruption in Intel(R) Graphics Drivers (high 7.8)
- [CVE-2020-0508](https://insights.sbomify.com/CVE-2020-0508/): Privilege escalation in Intel(R) Graphics Drivers (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32739 and fix it if it is affected.

What it is: CVE-2025-32739 is a low-severity denial of service vulnerability in Intel Graphics Driver, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32739 in the wild and no public exploit code.

Affected product: Intel Graphics Driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32739/ (Markdown: https://insights.sbomify.com/CVE-2025-32739/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32739
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32739
- OSV: https://osv.dev/vulnerability/CVE-2025-32739

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32739/
Summaries are generated and may contain mistakes; the official description above is the record.