CVE-2026-40705 · Infrastructure
NO FIX YET · SEE WHAT TO DO
The Intel NPU driver before 32.0.100.4778 has improper resource locking in its Ring 1 device driver code. A local, authenticated user with low-complexity access can cause a denial of service, with no confidentiality or integrity impact.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems with an Intel NPU and an NPU driver older than 32.0.100.4778 are exposed. The attacker needs a local authenticated account on the machine, so shared workstations and multi-user hosts matter most. Machines without an Intel NPU or with the fixed driver can skip it.
Not affected if fixed-driver, no-intel-npu, no-local-users
Who cares intel, laptops, npu-driver, windows
32.0.100.4778 as affected32.0.100.4778 or laterImproper resource locking for the Intel(R) NPU Drivers before version 32.0.100.4778 within Ring 1: Device Drivers 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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.