Intel NPU Driver CVE-2026-20731

Exploitation requires a local, authenticated user session with at least low-privilege access (PR:L per the CVSS 4.0 vector). No elevated or administrative rights are needed. No special attack requirements (AT:N) beyond standard local access apply - no specific non-default configuration, network service, or kernel module state is cited as a prerequisite. The flaw resides in the Ring 3 user-application interface, meaning any local user capable of invoking NPU driver calls (e.g., via an AI runtime library, direct syscall, or ioctl) is a potential threat actor. What limits exploitation: remote exploitation is categorically not possible (AV:L); the attacker must have physical or remote shell access to the host; the impact is confined to denial of service with no confidentiality loss and only minor integrity impact on the vulnerable system, with no subsequent system impact (SC/SI/SA all N).

The CVSS 4.0 score of 6.9 with vector AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N presents a consistent picture: a local, low-complexity, low-privilege denial-of-service with no confidentiality impact and minimal integrity side-effects. The attack is not remotely exploitable, which is the single most important risk-reducing factor. No EPSS data was provided, and the vulnerability is absent from the CISA KEV catalog, indicating no confirmed active exploitation. No public proof-of-concept code has been identified. The subsequent system impact metrics (SC/SI/SA all N) confirm no meaningful lateral blast radius. Taken together, this is a credible but contained risk: organizations running Intel NPU-equipped hardware where unprivileged users have local sessions (shared workstations, developer machines, AI inference appliances) face the highest practical exposure. Server environments where NPU driver access is tightly controlled present substantially lower risk. The primary concern is service disruption rather than data compromise.

A local user with a standard (non-root, non-admin) account on an Intel Core Ultra system submits a malformed or oversized buffer through the NPU driver's user-space API - for example, via a crafted AI inference workload or a direct ioctl call - triggering the CWE-119 buffer restriction flaw and crashing the NPU driver or causing system instability. No public proof-of-concept code has been identified at time of analysis, meaning successful exploitation currently requires knowledge of the specific buffer boundary flaw in the driver interface.