NVIDIA Display Driver EUVD-2026-90166

Exploitation requires local access to the NVIDIA GPU Display Driver kernel module (the ability to interact with the GPU device / issue driver commands on an affected Windows or Linux system running GeForce, RTX/Quadro/NVS, or Tesla drivers). Limiting factors: high attack complexity (AC:H) because the use-after-free depends on winning a timing/command-sequence race that is not reliably reproducible, and - if the vendor's AV:P is correct - physical or direct console-level access rather than remote or ordinary remote-desktop access. No user interaction is required. Note the description does not state an authentication requirement and the vendor vector uses PR:N, but the AV:P designation is anomalous versus sibling CVEs and should be confirmed with NVIDIA bulletin 5861.

All exploitation signals point to a low-to-moderate real-world priority despite the memory-corruption impact. The vendor CVSS 3.1 vector (AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H = 6.4) is notably WEAKER than the AV:L/AC:L/PR:L/7.8 pattern shared by the other bulletin-5861 GPU-driver UAF CVEs (e.g. CVE-2026-47590/47589/47594) - the AV:P (physical) attack vector is the key anomaly and looks questionable for a kernel-module use-after-free normally triggered by a local process issuing driver commands; this likely should be AV:L and should be verified against NVIDIA's security bulletin. There is no EPSS score, no CISA KEV listing, and no public POC provided, so this is 'no public exploit identified at time of analysis.' Combined with AC:H (a UAF race/sequence that is hard to win reliably), this reads as a real but low-probability, non-widespread issue rather than an urgent priority. The CWE-416 impact ceiling (code execution / EoP) keeps it worth patching in multi-user, VDI, or cloud-GPU environments, but no signal indicates imminent mass exploitation.

A local attacker with the ability to interact with the GPU kernel driver issues a crafted sequence of driver commands (or exercises a specific ioctl path) to free a kernel object while a dangling reference remains, then reclaims the freed allocation to corrupt kernel memory. Winning the race is difficult (AC:H), and if the vendor's AV:P is accurate, physical/console-level access is additionally required. No public exploit code is available.