Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local authenticated user session
-
DeliveryAccess Ring 3 NPU driver interface
-
ExploitSubmit crafted input triggering improper condition
-
ExecutionDriver fails exceptional condition check
-
PersistNPU driver crashes or hangs
-
ImpactAvailability impact to NPU and dependent workloads
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Unusual condition handling
|
| Exploitation Conditions | Exploitation requires a locally authenticated user-level session (Ring 3 / user application space) on a system running an affected version of the Intel NPU Driver. The CVSS 4.0 vector specifies PR:L (low privilege - any authenticated, non-root/admin user), AV:L (local access - shell, physical, or equivalent), and AT:N (no special attack requirements such as race conditions or non-default configuration). No user interaction from a privileged user is required after the attacker has local access. Exploitation is limited by the requirement for local access and an authenticated session; network-adjacent or remote unauthenticated exploitation is not possible based on the AV:L vector. Systems without Intel NPU hardware or without the NPU driver installed are not affected. |
| Impact | The CVSS 4.0 score of 6.9 reflects a moderate-severity, locally-exploitable DoS. The attack vector is local (AV:L), requiring physical or remote shell access with at minimum a low-privileged authenticated session (PR:L), which substantially limits opportunistic exploitation over the network. Attack complexity is low (AC:L) and no special attack requirements apply (AT:N), meaning exploitation is straightforward once local access is achieved. EPSS data is not provided; given the local-only vector and absence of KEV or POC, real-world exploitation probability is assessed as low at this time. There is no confidentiality impact, and integrity impact is limited to low - the primary concern is availability, likely manifesting as a driver crash or system hang affecting NPU functionality. The flaw is more concerning in shared multi-user environments (e.g., enterprise workstations, AI inference servers) where a low-privileged user could disrupt NPU workloads. No conflicting signals exist between the description and CVSS vector - both consistently indicate local, authenticated, low-complexity exploitation. No KEV listing and no POC are identified, supporting a standard patch-cycle response rather than emergency remediation. |
| Exploit ScenarioDerived | A low-privileged local user on an Intel NPU-equipped workstation or AI inference server calls an NPU driver interface with a crafted input that triggers the unhandled exceptional condition in the driver. The driver fails to properly check the condition (CWE-754), leading to a crash or hang of the NPU driver stack, denying NPU availability to all users on the system. No public exploit code has been identified, but the low attack complexity means a motivated local attacker could develop an exploit with modest reverse-engineering effort. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Denial of service in Intel(R) NPU Driver affects all versions via an improper conditions check (CWE-754) reachable from Ring 3 (user applications). A locally authenticated, low-privileged user can trigger the flaw without any special attack prerequisites or user interaction, resulting in high availability impact to the vulnerable system. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; however, the low complexity of exploitation combined with the growing deployment of NPU-equipped Intel platforms warrants prompt patching.
RemediationAI
The primary remediation is to apply the updated Intel NPU Driver version referenced in Intel Security Advisory INTEL-SA-01456 at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01456.html; no specific fix version number is independently confirmed in the available data beyond the advisory reference itself, so consult the advisory directly for the exact patched driver version. If immediate patching is not feasible, a compensating control is to restrict local user access to NPU device interfaces - for example, by limiting access to the relevant device node (e.g., /dev/accel or equivalent) to privileged accounts only; this trades off NPU availability for untrusted users against the DoS risk. In shared or multi-user environments, reducing the number of accounts with local interactive access (least privilege) limits the pool of potential exploiters. Disabling the NPU driver entirely is a last-resort option that eliminates the attack surface but also disables hardware AI inference acceleration on the platform.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Intel NPU (Neural Processing Unit) Driver is a kernel-mode driver exposing AI inference acceleration hardware to user-space applications (Ring 3). CWE-754 - Improper Check for Unusual or Exceptional Conditions - indicates the driver fails to validate an edge-case condition before acting on it, a common root cause of driver-level DoS when userspace input reaches kernel code paths without adequate sanitization. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) confirms the flaw is exploitable locally with no attack-specific requirements (AT:N), meaning no race condition, ASLR bypass, or special system state is needed. The CPE entry (cpe:2.3:a:n/a:intel(r)_npu_driver:*:*:*:*:*:*:*:*) covers all versions without version bounding, indicating the flaw is present across the entire release history to date. The integrity impact is low (VI:L) alongside the high availability impact (VA:H), consistent with a condition that may corrupt a bounded state before crashing the driver. Subsequent-system impacts (SC/SI/SA) are all None, placing the blast radius within the local user session or the NPU device stack.
Know when N A gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
Local vector and low privilege per description and CVSS 4.0; unchanged scope as subsequent-system impacts are all None; high availability and low integrity mirror the 4.0 vulnerable-system metrics.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Improper conditions check for the Intel(R) NPU Driver for all versions 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 (low) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
EUVD-2026-56492
GHSA-vfmv-9397-c37w
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB