# CVE-2025-26402: Denial of service in Intel(R) NPU Drivers

> An unprivileged local attacker can cause a denial of service in Intel NPU drivers due to a protection mechanism failure.

- **Severity:** Medium 6.8 (`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`)
- **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:** Yes
- **Published:** 11 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-26402, GHSA-q6mj-q5j8-3m24

## What is CVE-2025-26402?

CVE-2025-26402 is a medium-severity denial of service vulnerability in Intel(R) NPU Drivers, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Protection mechanism failure for some Intel(R) NPU Drivers within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

Apply the vendor's patch.

## Is CVE-2025-26402 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26402 is a medium-severity denial of service vulnerability in Intel(R) NPU Drivers, published on 11 Nov 2025. 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-26402 in the wild and no public exploit code.

Affected product: Intel(R) NPU Drivers. 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-26402/ (Markdown: https://insights.sbomify.com/CVE-2025-26402/index.md)
```

## Sources

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

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