Quick answers
- Is CVE-2026-40705 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40705 being exploited in the wild.
- How severe is CVE-2026-40705?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Intel NPU Driver for Linux before 1.33.0; Intel NPU Driver for Windows before 32.0.100.4778.
- Is there a fix for CVE-2026-40705?
- Yes: fixed in NPU Driver for Windows 32.0.100.4778; NPU Driver for Linux 1.33.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40705 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-40705?
- Check whether you run Intel NPU Driver for Linux or Intel NPU Driver for Windows at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: NPU Driver for Windows 32.0.100.4778; NPU Driver for Linux 1.33.0
Technical details
The Windows NPU Driver before version 32.0.100.4778 has improper resource locking in Ring 1 device driver code, allowing an authenticated local attacker with low complexity to trigger a denial of service condition via local access without user interaction. The vulnerability impacts system availability (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, CVSS score 6.8) and is fixed in version 32.0.100.4778.
Affected products
- Intel NPU Driver for Windows before 32.0.100.4778
- Intel NPU Driver for Linux before 1.33.0
Timeline
- 2026-11-10: disclosed
- 2026-11-10: patched