NVIDIA Display Driver CVE-2026-47603

Requires the attacker to already have local, low-privileged code execution on a system running the affected NVIDIA GPU Display Driver (kernel-mode component) for Windows or Linux; exploitation targets another process's GPU channel state. No user interaction and no elevated privileges are needed beyond the initial low-privilege foothold. Practical impact is materially limited to multi-user or multi-tenant deployments (VDI, cloud-GPU, shared workstations) where another process's GPU data is valuable; on single-user machines cross-process disclosure has little consequence. Impact is confined to information disclosure - no integrity or availability effect.

This is a genuine but modest-severity local information-disclosure issue, not a high-priority emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 5.5 Medium) is internally consistent with the description: exploitation requires local access and existing low-privilege code execution, and the only impact is confidentiality (C:H) - there is no integrity or availability impact (I:N/A:N), so no code execution or privilege escalation is claimed. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active or automatable exploitation. The 'Authentication Bypass' tag overstates the issue - this is an authorization (CWE-862) gap allowing one local process to read another process's GPU channel state, not an authentication bypass. Real priority is elevated only in multi-tenant contexts (VDI, cloud-GPU, shared workstations) where cross-process/cross-tenant memory confidentiality matters; on single-user endpoints the practical risk is low.

A local attacker who already has the ability to run low-privileged code on a shared GPU host (e.g., a VDI session, a cloud-GPU tenant, or a multi-user workstation) invokes the vulnerable kernel-mode driver interface to read the GPU channel state belonging to another user's process, harvesting sensitive rendered or computed data. No user interaction is required, but prior local code-execution access is a precondition. No public exploit code is identified at time of analysis.