Geforce
Monthly
Local privilege escalation, code execution, denial of service, information disclosure, and data tampering are possible in NVIDIA GPU Display Driver for Linux due to a use-after-free in the open-source kernel module's event-delivery path. An authenticated local user with access to NVIDIA GPU device nodes can race asynchronous event delivery against file close (CVSS 7.0, AV:L/AC:H/PR:L/UI:N), though the high attack complexity makes success non-deterministic and typically requires repeated attempts; no public exploit has been identified at time of analysis. Risk is concentrated on Linux hosts using the affected open-source kernel module, particularly multi-tenant vGPU, VDI, and cloud GPU deployments.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Out-of-bounds write in the NVIDIA GPU Display Driver for Windows kernel module can let a local, authenticated low-privileged user execute code, escalate privileges, cause denial of service, disclose information, or tamper with data on affected GeForce, RTX/Quadro/NVS, and Tesla systems. Exploitation requires local access to the GPU-equipped Windows host plus a low-privileged account able to reach the kernel module, and the high attack complexity means it is not reliably one-shot; multi-user, VDI, and cloud/virtual-GPU environments are the main risk. No public exploit identified at time of analysis, and CVSS is 7.0 with high confidentiality, integrity, and availability impact.
Denial of service and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.
An out-of-bounds read in the NVIDIA Display Driver for Windows kernel module allows local attackers to cause denial of service and disclose sensitive kernel memory. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver lines on Windows; exploitation requires local access with no elevated privileges or user interaction. No public exploit code has been identified, and the vulnerability is not remotely exploitable.
Authenticated low-privileged local users can bypass cryptographic signature verification in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux when the system is under memory pressure, leading to data tampering and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver branches on Linux; no public exploit code has been identified at time of analysis. Our assessment rates this as a genuine but bounded-priority local issue because the attacker must reliably induce a low-memory kernel state at the moment of verification, making exploitation opportunistic rather than dependable.
Information disclosure and data tampering can be achieved by a local low-privileged attacker exploiting a missing authorization check in the NVIDIA GPU Display Driver for Windows kernel module. Affected products include the GeForce, RTX/Quadro/NVS, and Tesla driver branches on Windows; exploitation requires local authenticated access (PR:L) and no user interaction (UI:N). No public exploit code or active exploitation has been identified at time of analysis; the CVSS score is 7.3 with scope change (S:C) that amplifies risk in multi-user or cloud-GPU environments.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux can be achieved by an unprivileged local user through the open-source kernel module's DMA-BUF import path, where importing a read-only buffer from another device's DMA-BUF exporter improperly preserves memory access permissions. Successful exploitation can result in code execution, privilege escalation, denial of service, information disclosure, and data tampering, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, and no CISA KEV entry is present in the provided data.
Local privilege escalation and kernel-level code execution in the NVIDIA GPU Display Driver for Windows and Linux, where the kernel-mode layer follows an error-handling path that operates on an improperly initialized resource (CWE-908). The flaw is reachable by an authenticated, low-privileged local user (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) on any host where the affected driver is installed and loaded, granting full confidentiality, integrity, and availability impact within the kernel-mode driver's scope. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); risk is concentrated on shared multi-tenant GPU hosts such as VDI, cloud GPU instances, and vGPU guests where untrusted local users coexist with the driver, and success may be probabilistic because the attacker must reliably trigger the failing error path.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in the NVIDIA GPU Display Driver's open-source kernel module lets an unprivileged local user trigger a use-after-free in the Resource Server map cleanup path via a missing self-reference guard, yielding code execution, privilege escalation, denial of service, information disclosure and data tampering (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, CWE-416). Affected are Windows and Linux hosts running the open-source kernel module variant of the driver, spanning GeForce, RTX/Quadro/NVS and Tesla product lines per the published CPEs; exploitation requires only a normal local account and no user interaction, but is strictly local with no network vector. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical risk is highest in shared or multi-tenant GPU environments (vGPU, VDI, cloud GPU) where gaining kernel-level control of the GPU driver crosses a meaningful tenant boundary.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a use-after-free (CWE-416) reachable by a low-privileged local user who can issue a crafted sequence of driver commands. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high, with the greatest risk in shared or virtualized GPU deployments where guest-driver or virtual GPU manager isolation may be broken. No public exploit code or confirmed active exploitation is identified in the available data, and EPSS is not provided; exploitation requires local access and construction of the specific command sequence.
Local privilege escalation in NVIDIA Display Driver for Windows allows an authenticated low-privileged user to trigger a stack-based out-of-bounds write in the kernel mode layer, potentially leading to code execution, privilege escalation, and denial of service. Affected systems include Windows hosts with GeForce, RTX/Quadro/NVS, or Tesla drivers, as well as the Guest Driver in virtualized deployments. No public exploit code or active exploitation has been identified at time of analysis, and the flaw requires local access, making it most relevant to shared multi-tenant environments.
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authenticated unprivileged user to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPUs, as well as Guest Driver and vGPU Manager deployments. With a CVSS score of 7.8, the vulnerability requires local access and low privileges (CVSS vector AV:L/AC:L/PR:L/UI:N), making it primarily a risk in multi-user or shared-GPU environments; no public exploit has been identified at time of analysis, and patched driver branches are available in NVIDIA security bulletin 5861.
Local privilege escalation in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows an unprivileged local user to bypass read-only memory protection and gain write access to memory the driver marked read-only, which can result in kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering. Exploitation requires the attacker to already hold low-privileged local access on an affected Linux host (CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N, score 7.8) with no user interaction and no network vector; the risk is greatest on shared, multi-tenant vGPU, VDI, and cloud-GPU hosts where crossing the user-to-kernel boundary breaks tenant isolation. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but NVIDIA has published a fix through security bulletin 5861. This is a genuine local privilege-escalation risk rather than an emergency, and it should be prioritized on multi-tenant GPU infrastructure.
Local privilege escalation in NVIDIA Display Driver for Windows and Linux allows an unprivileged local attacker to trigger a use-after-free condition by issuing a crafted sequence of driver commands, potentially achieving code execution, privilege escalation, denial of service, or information disclosure. The vulnerability affects systems with GeForce, RTX/Quadro/NVS, or Tesla GPUs running vulnerable driver versions. No public exploit identified at time of analysis.
Local privilege escalation and memory corruption in NVIDIA GPU Display Driver on Windows and Linux, affecting GeForce, RTX/Quadro/NVS, and Tesla lines. An unprivileged local user can trigger a use-after-free (CWE-416) by issuing a specific sequence of driver commands, leading to potential code execution, privilege escalation, denial of service, or information disclosure. Requires local access and low privileges (AV:L/PR:L) with no user interaction (UI:N); no public exploit identified at time of analysis. Risk is highest in multi-user or shared-GPU environments such as VDI, terminal servers, and cloud/virtualized GPU hosts.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, unprivileged user to trigger a use-after-free condition by issuing a specific sequence of driver commands, potentially leading to code execution, privilege escalation, denial of service, and information disclosure. The vulnerability affects GeForce, RTX/Quadro/NVS, and Tesla GPU drivers, including guest-VM vGPU deployments, and requires local access with low privileges. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Use-after-free in the NVIDIA GPU Display Driver for Linux allows a local, unprivileged user to corrupt driver memory by racing or abusing object lifetime handling, with a successful exploit potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The flaw scores 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is confined to local attackers who already hold an account on the GPU host, with no network vector and no user interaction required. This is a genuine but not emergency-grade issue: no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so realistic exposure is concentrated on shared or multi-tenant GPU systems - VDI desktops, cloud GPU instances, and HPC nodes - where untrusted users share a single driver instance.
An integer underflow (CWE-191) in the kernel-mode component of the NVIDIA GPU Display Driver for Windows lets a local, authenticated low-privileged user corrupt kernel memory in a way that can lead to code execution, privilege escalation, denial of service, information disclosure, or data tampering (CVSS 3.1: 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The issue affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches and is not network-reachable, so an attacker must already be able to run code as a normal user on the host. There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is concentrated on multi-user, VDI and cloud-GPU hosts where an unprivileged tenant shares the same machine as the vulnerable driver, while single-user desktops where the attacker must already hold a foothold face lower marginal risk.
Type confusion in the kernel-mode component of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution to corrupt kernel memory and potentially escalate to SYSTEM, crash the machine (BSOD/DoS), disclose kernel memory, or tamper with data. The issue is rated CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning the attacker must be local and authenticated with low privileges and no user interaction is required, and it affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is an access-gated local privilege-escalation risk rather than a remotely reachable mass-exploitation threat.
Local privilege escalation in NVIDIA Display Driver on Windows allows an authenticated low-privileged user to trigger a use-after-free in the kernel-mode driver, potentially enabling code execution with SYSTEM privileges, denial of service, information disclosure, or data tampering. The vulnerability requires local access and high attack complexity (AC:H) due to race conditions or kernel-pool reclamation, making reliable exploitation non-trivial, and it is not known to be actively exploited. The highest risk is in shared multi-user, VDI, or cloud-GPU environments where crossing a trust boundary from low-privileged user to kernel is significant.
Incorrect buffer size calculation in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution on the host to escalate to kernel-level privileges, with downstream risk of code execution, denial of service, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla data-center, and vGPU/Virtual GPU Manager drivers, and rates CVSS 3.1 base 7.8 (AV:L/AC:L/PR:L/UI:N) - it is strictly local, not remotely triggerable, so exposure is limited to shared workstations, multi-tenant vGPU/VDI environments, and cloud-GPU nodes where an untrusted party can already run code. No public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows allows an authenticated attacker with low-privileged code execution to exploit an integer overflow (CWE-190) in the kernel module, potentially achieving code execution, denial of service, information disclosure, and data tampering. The flaw requires local access (AV:L) and low privileges (PR:L) with no user interaction, affecting systems with GeForce, RTX/Quadro/NVS, or Tesla drivers. No public exploit code or active exploitation has been identified at the time of analysis; the CVSS 3.1 base score is 7.8 (HIGH).
Local code execution and denial of service on Windows systems with affected NVIDIA GPU Display Drivers stem from an integer overflow in the display driver's DIAG escape handler that results in an out-of-bounds write (CWE-787). An unprivileged local user (CVSS PR:L) can trigger the flaw via a device I/O call to the handler; no user interaction is required, and exploitation is confined to the local machine, meaning an attacker must already have a foothold. No public exploit identified at time of analysis (and no CISA KEV entry), but the shared-system impact-multi-user workstations, VDI, and cloud GPU instances-raises the risk profile.
An out-of-bounds write in NVIDIA NVAPI for Windows allows a locally authenticated attacker holding standard user privileges to corrupt memory by invoking NVAPI entry points, potentially leading to code execution, elevation of privileges, information disclosure, denial of service, or data tampering. The flaw affects hosts running the NVIDIA GPU driver package on Windows - including GeForce, RTX/Quadro/NVS, and Tesla driver-equipped systems - with a CVSS 3.1 base score of 7.8 (HIGH) under vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. No public exploit code and no confirmed active exploitation (CISA KEV) have been identified at time of analysis, but the local-only, low-privilege prerequisite makes shared and multi-tenant GPU/VDI hosts the most exposed environment.
Type confusion in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a local low-privileged user (CVSS vector AV:L/AC:L/PR:L/UI:N) who can reach the driver's device-node/ioctl interface to trigger memory corruption with high impact across confidentiality, integrity, and availability, potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The CVSS 3.1 base score of 7.8 reflects a local attack vector paired with uniformly high impacts rather than any remote reachability, and despite the 'RCE' tag in the source metadata the vulnerability is not remotely exploitable. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and no EPSS or CISA KEV signal was provided.
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
Local privilege escalation in NVIDIA GPU Display Driver for Windows (CUDA driver component) allows an authenticated attacker with low privileges to execute arbitrary code by planting a malicious library in an uncontrolled search path. Affected products include GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest driver branches. No public exploit identified at time of analysis; exploitation requires local access and write permissions to a directory resolved by the driver's search path, making it most relevant on shared multi-user or VDI/cloud-GPU hosts.
A type-confusion flaw in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux lets a local, low-privileged user who can open the driver's device nodes and issue ioctls trigger memory corruption by winning a handle-recycle race, yielding kernel-level code execution, privilege escalation, denial of service, information disclosure and data tampering. Affected platforms are the Linux driver branches covering GeForce, RTX/Quadro/NVS, Tesla/data-center GPUs and the vGPU guest driver and Virtual GPU Manager (CVSS 3.1 base 7.8; our independent assessment rates it AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, i.e. 7.0, because the race window makes exploitation timing-sensitive rather than deterministic). This is a local privilege-escalation-class issue with no remote vector: no public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), though it is most consequential on multi-user, VDI and cloud/virtualized GPU hosts where untrusted tenants share a single driver instance.
A NULL pointer dereference in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a locally present, low-privileged authenticated user to crash the driver - and potentially the kernel - by supplying a crafted request to the kernel-mode driver layer (for example via device ioctls). Affected platforms span the GeForce, RTX/Quadro/NVS, and Tesla driver lines on Linux, and the 'Guest Driver' / 'Virtual GPU Manager' tags indicate the vGPU path is also in scope, so a guest session inside a virtualized vGPU deployment is a valid attack position. The vendor claims the flaw 'might' lead to code execution, privilege escalation, information disclosure, and data tampering, but the reliably achievable outcome is a denial-of-service crash; there is no CISA KEV listing, no EPSS score provided, and no public exploit identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to trigger an out-of-bounds write in kernel memory via a crafted ioctl call with an unvalidated buffer size, enabling code execution, privilege escalation, information disclosure, and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla drivers, as well as Guest Driver and Virtual GPU Manager components, with highest risk in multi-tenant GPU environments such as VDI and cloud/HPC deployments. No public exploit identified at time of analysis; CVSS 3.1 score is 7.8 (local, low privileges, no user interaction).
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated unprivileged user to trigger a use-after-free in the kernel mode layer, potentially achieving code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw is reachable only by a locally authenticated low-privileged account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) that can issue ioctls to the GPU kernel-mode device interface; there is no remote attack path and no user interaction is required once a foothold exists. The 'Guest Driver' classification makes the issue most consequential in virtualized/vGPU and multi-tenant datacenter environments, where a low-privileged guest can reach the shared GPU driver. No public exploit identified at time of analysis, and the vendor advisory is the authoritative source for fixed driver versions.
Local privilege escalation in NVIDIA's GPU Display Driver (GeForce, RTX/Quadro/NVS, and Tesla, on both Windows and Linux) allows an authenticated low-privileged local user to reach GPU memory belonging to another process, enabling code execution, escalation of privileges, data tampering, denial of service, and information disclosure. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) there is no remote or network path; the flaw is most consequential on shared, multi-user, VDI, or multi-tenant GPU hosts where cross-process GPU memory isolation is the boundary between users and tenants. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the provided vendor reference points to NVIDIA's product security advisory (2026/5861) rather than a fixed driver version named in this data set.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel mode layer allows an authenticated, unprivileged user to trigger a double-free of imported memory state, potentially leading to code execution, denial of service, information disclosure, and data tampering. The flaw requires local access and a low-privilege account; no public exploit code or active exploitation has been identified at time of analysis. The CVSS 3.1 score is 7.8 (HIGH).
Local privilege escalation, code execution, denial of service, and information disclosure in NVIDIA GPU Display Driver on Windows and Linux stem from an integer overflow (CWE-190) in the kernel-mode layer that an unprivileged user can trigger to cause an out-of-bounds write. Exploitation requires local access with an existing low-privilege account (authenticated, PR:L) on a host with an affected GeForce, RTX/Quadro/NVS, or Tesla driver; the CVSS v3.1 base score is 7.8 (High) with a local attack vector (AV:L/AC:L/PR:L/UI:N). No public exploit code or CISA KEV entry was identified at the time of analysis, but the flaw is genuine and actionable for local privilege escalation if the vulnerable driver interface is reachable.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows an unprivileged local user to corrupt kernel memory, which can lead to code execution in the kernel, privilege escalation, denial of service, information disclosure, or data tampering. Systems running GeForce, RTX/Quadro/NVS, or Tesla driver packages on either operating system are affected; per the CVSS vector (AV:L, PR:L, UI:N) the flaw is reachable only by a user who already has local code execution on the host, making it a local privilege-escalation primitive rather than a remote entry point. No public exploit has been identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux stems from a missing authorization check in the kernel mode layer, allowing an unprivileged local user to modify privileged configuration and potentially achieve code execution, escalation of privileges, denial of service, information disclosure, and data tampering. Exploitation requires a pre-existing local low-privileged foothold (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), such as an unprivileged account on a host or inside a guest VM using the NVIDIA guest driver or Virtual GPU Manager, so this is an escalation primitive rather than a remote initial-access vector. No public exploit code is identified and no CISA KEV active exploitation is confirmed at time of analysis, but the high confidentiality, integrity, and availability impacts and broad affected driver families make patching a priority.
Use-after-free in the NVIDIA GPU Display Driver kernel mode layer (Windows and Linux) lets a local user who already holds low-privileged code execution on the host trigger a memory-corruption condition inside the kernel driver, with the potential for code execution, privilege escalation, information disclosure, data tampering, and denial of service. Affected platforms span consumer and professional GPU lines (GeForce, RTX/Quadro/NVS, Tesla) as well as the vGPU components, where a malicious or compromised guest can exercise the vulnerable path through the Guest Driver and Virtual GPU Manager. The attack is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, score 7.8), requires no user interaction and no non-default configuration beyond having the driver installed, and there is no public exploit identified at time of analysis - no KEV entry and no proof-of-concept code is referenced in the available data.
Local privilege escalation in NVIDIA GPU Display Drivers for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU) allows an unprivileged local user to execute code in kernel mode by supplying an untrusted pointer that the driver dereferences without validation. Affected hosts include multi-user and virtualized Windows systems with default driver installations, where exploitation can lead to escalation to SYSTEM, denial of service, information disclosure, and data tampering. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; the CVSS 3.1 base score is 7.8 (High).
A locally-triggered out-of-bounds write in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-level privileges on a Windows or Linux host corrupt kernel memory, with the potential for code execution in kernel context, escalation of privileges, denial of service, information disclosure and data tampering. The affected driver ships by default across the GeForce, RTX/Quadro/NVS, Tesla and Virtual GPU Manager product lines, so any host with a current NVIDIA driver installed is in scope, but exploitation is not remote: an attacker must first obtain code execution on the target (an authenticated local user, a compromised low-privileged process, or sandboxed code with driver access) and then develop a reliable kernel corruption exploit. CVE-2026-47548 carries a vendor/NVD CVSS 3.1 vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8, High); no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Local attackers with low-privileged code execution can trigger an out-of-bounds read (CWE-125) in the kernel-mode layer of the NVIDIA GPU Display Driver on Windows and Linux, which may lead to escalation of privileges, code execution, denial of service, information disclosure, and data tampering. This locally exploitable flaw (CVSS 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) affects GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager products, and no public exploit has been identified at the time of analysis. A vendor advisory with remediation guidance is available from NVIDIA via its product security page.
Integer underflow in the kernel-mode layer of NVIDIA GPU Display Driver for Windows and Linux allows a local attacker with low privileges to potentially achieve code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Manager products, and exploitation requires local access (CVSS AV:L) with no user interaction (UI:N) but low privileges (PR:L). No public exploit code has been identified at time of analysis, and there is no indication of active exploitation.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged authenticated user to corrupt kernel memory, with the potential to escalate privileges to kernel-level code execution, crash the system (denial of service), disclose information, or tamper with data. The flaw rates CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires pre-existing code execution as a standard user on a host with the driver loaded, but no user interaction and no non-default configuration; the vulnerable kernel-mode layer ships and loads by default once the driver is installed. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, but the affected GeForce, RTX/Quadro/NVS, and Tesla product families are extremely widely deployed, making this a genuine high-priority patch-management item rather than an emergency.
Local attackers with low privileges can exploit an uninitialized pointer access flaw (CWE-824) in the firmware of NVIDIA Display Driver for Windows and Linux to achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering. The vulnerability requires local access (AV:L) and authenticated low-privilege credentials (PR:L); no public exploit identified at time of analysis. Affected products include GeForce, RTX/Quadro/NVS, and Tesla product lines, including vGPU Manager deployments.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds low-privilege code execution corrupt kernel memory, with potential outcomes of privilege escalation, arbitrary code execution, denial of service, information disclosure and data tampering (CWE-787, CVSS 7.8). The assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H shows low attack complexity and no user interaction, but the attack is strictly local: an attacker must first have a foothold on the host, or on a guest in a vGPU configuration, which confines it to privilege-escalation and sandbox-escape scenarios rather than remote mass exploitation. No public exploit code and no confirmed active exploitation were identified at time of analysis (no public exploit identified at time of analysis), so this is a genuine local privilege-escalation priority despite the absence of exploitation signals, and it warrants prompt patching on endpoint, workstation, and multi-tenant virtual-desktop estates.
A use-after-free (CWE-416) in the NVIDIA GPU Display Driver for Windows and Linux lets a local unprivileged user free and then re-reference a driver-managed memory object, potentially yielding code execution in kernel context, privilege escalation, data tampering, denial of service, and information disclosure. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and affects GeForce, RTX/Quadro/NVS, and Tesla product lines; the 'Guest Driver' tag indicates the vulnerable path may also be reachable from inside a virtualized guest, making guest-to-host or guest-context escalation a relevant scenario. Exploitation requires that the attacker already hold a local foothold with normal user privileges on a host with the affected driver installed and the GPU device interface exposed - there is no remote/network vector - and at time of analysis no public exploit code and no confirmed active exploitation have been identified, so this is a priority local privilege-escalation issue rather than an imminent, opportunistically exploited threat.
Local kernel stack memory disclosure in NVIDIA GPU Display Driver for Windows and Linux allows an attacker who already has low-privilege authenticated code execution on the host to read kernel stack contents such as return addresses and pointers. Affected installations include GeForce, RTX/Quadro/NVS, and Tesla driver configurations, and the independent assessment rates the flaw as AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning high confidentiality impact without confirmed integrity or availability impact. No public exploit is identified at time of analysis, and no CISA KEV active exploitation is reported.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged user to read beyond the bounds of kernel heap memory, producing information disclosure and denial of service, with potential for privilege escalation, code execution, and data tampering if the read primitive is successfully leveraged. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla product families on systems with the vulnerable driver branch installed, and exploitation requires an attacker to already hold local access to the host (per the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N vector, base 7.8), with no user interaction needed. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so exploitation is currently expected to require a motivated local attacker rather than being broadly weaponized.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds a low-privileged execution context on the host read past the bounds of a kernel buffer, exposing kernel memory contents and creating a pathway toward further privilege escalation or data tampering. Exploitation is constrained to the local attack surface: the attacker must already be able to run code on the machine (AV:L, PR:L) and no user interaction or network path is involved, so despite the 7.8 headline score the practical risk is a local privilege/information-disclosure concern rather than a remotely reachable, mass-exploitable flaw. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the affected hardware spans GeForce, RTX/Quadro/NVS, and Tesla products, with an NVIDIA vendor advisory available.
Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer allows a user with standard privileges to trigger an out-of-bounds write in kernel memory, potentially achieving kernel-level code execution, denial of service, information disclosure and data tampering. The affected driver branches span NVIDIA GeForce, RTX/Quadro/NVS and Tesla families on both Windows and Linux, and the 'Guest Driver' tag indicates virtualized/vGPU and guest-VM driver deployments are also in scope, which matters for GPU-accelerated VDI and datacenter estates. Exploitation is constrained to the host: the CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), so an attacker must already have a foothold and the ability to run code as a low-privileged local user; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged local user to trigger an integer overflow in the kernel mode layer, resulting in an out-of-bounds write to GPU memory that can lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. Affected platforms include GeForce, RTX/Quadro/NVS, and Tesla drivers, with the 'Guest Driver' tag indicating that VM guests with GPU access are also in scope for guest-to-host or in-guest escalation. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and the CVSS 3.1 score is 7.8 (AV:L/PR:L/UI:N).
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged user to trigger an incorrect conversion between numeric types in the kernel mode layer, potentially leading to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The vulnerability requires local access and low-level privileges (CVSS vector PR:L) with no user interaction, and it is not remotely exploitable. No public exploit code has been identified at time of analysis, but the risk is materially higher on shared or multi-tenant GPU hosts such as VDI, vGPU, or Tesla datacenter deployments where untrusted users can reach the driver.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows and Linux lets a low-privileged local user trigger an out-of-bounds array access in the kernel mode layer, potentially yielding code execution in kernel context, denial of service, escalation of privileges, information disclosure and data tampering. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), meaning the attack is strictly local and requires only low-privileged authenticated code on the host, with no user interaction and low complexity - so any unprivileged process able to reach the affected kernel-mode interface on a system running GeForce, RTX/Quadro/NVS or Tesla drivers (or a vGPU host reachable from a guest) can attempt it. There is confirmed actively exploited (CISA KEV) status: no - the CVE is not in KEV and no public exploit code has been identified at time of analysis, so early patching is key while exploitation activity has not yet been observed.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows allows a low-privileged local user - or a sandboxed process or guest with access to the driver interface - to trigger a use-after-free in the kernel-mode layer, potentially achieving kernel code execution, privilege escalation, denial of service, information disclosure, or data tampering. The assessed vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) means the attacker must already have code running on a host with an affected NVIDIA driver installed, but needs no user interaction and faces low complexity once local access exists; per the affected CPEs, the GeForce, RTX/Quadro/NVS, and Tesla branches are in scope, and the associated Guest Driver and Virtual GPU Manager tags mean a virtual-GPU guest may also be able to reach the kernel layer. No public exploit code or confirmed active exploitation was identified at the time of analysis, and hosts without an NVIDIA GPU/driver installed are unaffected.
Local code execution, privilege escalation, denial of service, information disclosure, and data tampering are possible on Linux systems running vulnerable NVIDIA GPU Display Drivers (GeForce, RTX/Quadro/NVS, and Tesla branches) because of a type-confusion flaw (CWE-843) in the outdated embedded cryptographic library used by the NGX updater. The assessed profile is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8): an attacker who already holds a low-privileged local account can reach the vulnerable updater code path, with no user interaction required and low complexity, but the flaw is not remotely reachable, so shared and multi-user hosts (VDI, HPC/Tesla compute clusters, and workstations with untrusted local users) are the realistic risk surface. No public exploit code has been identified at time of analysis, and the exact affected and fixed driver versions must be confirmed from NVIDIA's advisory.
Integer overflow in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager can be triggered by a low-privileged user inside a guest VM, causing memory corruption with high confidentiality, integrity, and availability impact. The vulnerability affects vGPU deployments on Windows and Linux hosts across GeForce, RTX/Quadro/NVS, and Tesla driver branches, and successful exploitation could enable code execution, denial of service, privilege escalation, information disclosure, or data tampering. No public exploit code or active exploitation has been identified in the provided intelligence at time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, low-privileged user to drive an out-of-bounds write in the driver's kernel-mode layer by supplying mismatched memory buffers during event buffer setup, with a successful exploit potentially leading to kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The affected code is the Linux kernel-mode component shipped with GeForce, RTX/Quadro/NVS and Tesla driver packages, and the same path can be reached by untrusted code inside a guest VM using the NVIDIA vGPU guest driver on a host running the Virtual GPU Manager. No public exploit code was identified and there is no confirmed active exploitation (CISA KEV) at time of analysis; the bug is local-only, requiring the attacker to already run code with at least low privileges on the host or in a guest, and it is not remotely reachable.
Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-privileged code execution on a Windows or Linux host - including code running inside a vGPU guest VM - drive the driver into an error path that mishandles reference counts, producing a use-after-free. The corrupted object is kernel memory, so successful exploitation can yield code execution, escalation of privileges, denial of service, information disclosure, and data tampering (CVSS 7.8, AV:L/AC:L/PR:L/UI:N); it is not remotely reachable and requires a vulnerable driver version to be installed. The GeForce, RTX/Quadro/NVS, and Tesla driver families are in scope, and no public exploit code has been identified at the time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux lets an already-authenticated, low-privileged user trigger a format string defect (CWE-134) and potentially achieve code execution, privilege escalation, data tampering, denial of service, and information disclosure; NVIDIA rates it 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack surface is strictly local - there is no remote vector - so real risk concentrates on multi-user and multi-tenant GPU systems such as HPC clusters, ML/AI training nodes, shared engineering workstations, and cloud GPU instances, where a low-privileged tenant could reach the driver while other users' data and the host remain in scope. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; the impact rating of total confidentiality, integrity, and availability loss is consistent with memory corruption inside a privileged driver context.
Local privilege escalation and kernel memory-safety compromise on Linux systems running NVIDIA GPU Display Drivers allow an unprivileged local user to cause improper release of kernel-mode memory resources, leaving a mapping accessible after the underlying memory has been reused. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver lines and carries a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning an attacker who already holds a local login can potentially achieve code execution, denial of service, information disclosure, privilege escalation, and data tampering without user interaction. No public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited, but the local-only vector makes it most dangerous on shared or multi-tenant GPU hosts where one unprivileged tenant could compromise the kernel and other workloads.
Local privilege escalation and memory-protection bypass in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to execute code at higher privilege, tamper with data, disclose information, or cause denial of service. The flaw is in the kernel-mode layer and affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver/Virtual GPU Manager deployments, with a CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N). No public exploit identified at time of analysis, and no CISA KEV active-exploitation signal is present; the assessed attack path requires prior local access on the host or inside a vGPU guest.
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest drivers) allows an authenticated local user to abuse improper permission handling in a kernel mode layer handler, enabling code execution, privilege elevation, and data tampering. CVSS 7.8 reflects high impact across confidentiality, integrity, and availability, but the attack vector is local and authenticated. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC marks technical impact as total.
Local privilege escalation in NVIDIA Display Driver for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest/manager components) stems from a time-of-check time-of-use (TOCTOU) race condition that can be abused by a low-privileged local user. Successful exploitation may yield code execution, privilege escalation, denial of service, information disclosure, or data tampering with scope change beyond the driver's security boundary. No public exploit identified at time of analysis; EPSS is 0.01% and SSVC exploitation status is 'none', so the practical risk is contingent on local access and winning a high-complexity race.
Local privilege escalation in NVIDIA Display Driver for Windows and Linux allows authenticated low-privilege users to improperly access GPU resources via a kernel mode layer flaw, potentially leading to code execution, privilege escalation, information disclosure, data tampering, and denial of service. The issue affects GeForce, RTX/Quadro/NVS, and Tesla product lines across multiple driver branches and carries a CVSS 7.8 (High) score. No public exploit identified at time of analysis, and EPSS probability is very low (0.01%), but the breadth of affected hardware and total technical impact warrant prompt patching.
Local privilege escalation in the NVIDIA Display Driver for Windows and Linux allows an authenticated low-privileged user to trigger an out-of-bounds write (CWE-787) in the kernel-mode driver, potentially leading to code execution, privilege escalation, information disclosure, data tampering, or denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla product lines, with NVIDIA confirming the vulnerability and releasing patched driver versions. No public exploit identified at time of analysis, and EPSS rates exploitation probability at just 0.01%.
Out-of-bounds read in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest drivers) allows a locally authenticated user to trigger denial of service and information disclosure. The flaw carries a CVSS 3.1 score of 7.1 (AV:L/AC:L/PR:L), and per CISA SSVC there is no public exploit identified at time of analysis (Exploitation: none), with EPSS at 0.01% indicating negligible near-term exploitation likelihood. NVIDIA has published fixed driver versions across all affected branches in advisory ID 5821.
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager branches) stems from an incorrect numeric type conversion (CWE-681) that produces a heap buffer overflow. A locally authenticated attacker with low privileges can trigger the flaw to achieve code execution, privilege escalation, information disclosure, data tampering, or denial of service. No public exploit identified at time of analysis, and EPSS is very low (0.01%, 1st percentile), but technical impact per SSVC is total.
Local privilege escalation and code execution in the NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest/Manager components) stems from a use-after-free memory corruption flaw (CWE-416) that a local low-privileged user can trigger to compromise the kernel-level driver. The scope-changed CVSS 8.8 score reflects that successful exploitation crosses a trust boundary, potentially yielding code execution, privilege escalation, information disclosure, data tampering, or denial of service. EPSS is 0.01% (1st percentile) and there is no public exploit identified at time of analysis, but a vendor patch is available across all affected branches.
Local attackers with low privileges can inject crafted text into the kernel log on Linux systems running the NVIDIA GPU Display Driver because the kernel mode layer fails to sanitize a supplied version string, leading to denial of service and data tampering. The vulnerability requires local access (AV:L) and low privileges (PR:L) with no user interaction, and has low impact on integrity and availability (I:L/A:L) with no confidentiality loss. No public exploit identified at time of analysis, and the overall risk is low despite the wide deployment of NVIDIA GPUs.
Denial of service in the NVIDIA GPU Display Driver for Windows and Linux occurs when a NULL pointer dereference is triggered in the kernel-mode layer, crashing or hanging the graphics subsystem on the affected host. Only systems with a physical NVIDIA GPU (GeForce, RTX/Quadro/NVS, or Tesla branches) running a driver older than the branch-specific fixed release are exposed, and exploitation requires an attacker who already holds HIGH privileges (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H), so an unprivileged local user cannot reach the vulnerable interface. There is no confidentiality or integrity impact, no public exploit code and no confirmed active exploitation (not in CISA KEV), and the EPSS score was not reported; the high-privilege prerequisite caps real-world priority at LOW despite the nominal MEDIUM CVSS.
Denial of service in NVIDIA GPU Display Driver on Windows and Linux is possible when a highly privileged local attacker reaches a firmware code path that dereferences a null pointer. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver branches prior to the fixes documented in NVIDIA bulletin 5861, with some older branches limited to Maxwell, Volta, and Pascal GPUs. The assessed vector is local and requires high privileges, with availability impact only; no public exploit identified at time of analysis, and the low CVSS score of 4.4 reflects those constraints.
Information disclosure in the NVIDIA GPU Display Driver kernel-mode component (Windows and Linux) lets an authenticated local user read another process's GPU channel state, because the driver performs missing authorization checks (CWE-862) when a process requests channel state it does not own. The flaw is rated CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so it requires a pre-existing local, low-privileged foothold and yields confidentiality impact only - no integrity or availability effect - and there is no public exploit identified at time of analysis. Practical risk concentrates on hosts where multiple security contexts share the same GPU, such as multi-user workstations, VDI, and cloud/virtual-GPU deployments; single-user desktops with one active GPU context gain little from this primitive, so the overall priority is low-to-moderate and locally scoped.
Local information disclosure in NVIDIA Display Driver for Windows and Linux allows an authenticated local user with low privileges to access another process's GPU channel state because the kernel-mode driver omits authorization checks. Affected platforms include NVIDIA GeForce, RTX/Quadro/NVS, and Tesla GPUs; the issue is rated CVSS 5.5 with high confidentiality impact but no integrity or availability impact. No public exploit was identified at time of analysis, and the practical risk is greatest in multi-user or multi-tenant GPU environments such as VDI and cloud-GPU deployments.
A NULL pointer dereference in the kernel-mode component of the NVIDIA GPU Display Driver for Windows allows a local attacker who can already execute low-privileged code on the host to crash the graphics kernel driver, taking down the display stack or bugchecking the whole machine. The flaw is confined to availability: per the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, there is no network path, no user interaction, and no confidentiality or integrity impact, so it cannot be used for code execution, privilege escalation, or data disclosure. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS/KEV signals are absent; the practical risk is concentrated on multi-user, VDI, or cloud-GPU Windows hosts where an unprivileged tenant could repeatedly disrupt the machine, making this a genuinely low-to-moderate priority issue despite the ubiquity of the affected hardware.
Denial of service in the NVIDIA GPU Display Driver for Windows kernel module allows a local low-privileged user to trigger improper locking, potentially crashing or hanging the system. The vulnerability affects GeForce, RTX/Quadro/NVS, and Tesla product lines, but exploitation is limited to local access with existing low-level privileges and no user interaction, resulting in availability impact only. No public exploit code or active exploitation has been identified at time of analysis, and the CVSS score is 5.5, making this a low-to-moderate priority issue despite the ubiquity of the driver.
Local, authenticated, low-privilege users on Linux hosts can cause a denial-of-service condition against the NVIDIA GPU Display Driver kernel-mode layer by repeatedly invoking an interface that emits unrate-limited error messages, leading to uncontrolled kernel log generation and resource exhaustion. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPU families running the Linux driver, as reflected in the NVIDIA CPE entries. Despite the moderate 5.5 CVSS score, this is a low-priority issue because exploitation requires local code execution with no remote or unauthenticated path, only availability is impacted, and no public exploit has been identified at time of analysis.
Denial of service in NVIDIA GPU Display Driver for Linux arises when a local authenticated low-privileged user exhausts the DRM VMA offset address space, causing uncontrolled resource consumption in the kernel mode layer. The issue is limited to Linux and to availability impact; exploitation requires an existing local foothold and cannot provide code execution, privilege escalation, or data disclosure. No public exploit was identified at time of analysis, and the assessed risk is low, though shared or multi-tenant GPU systems such as VDI, cloud GPU, and Tesla/vGPU deployments face the greatest practical disruption.
Kernel memory exhaustion in the NVIDIA GPU Display Driver for Linux allows a local, unprivileged user to repeatedly drive error-handling paths in the driver's kernel-mode layer so that leaked allocations accumulate until kernel memory is depleted, resulting in a denial of service on the affected host. The flaw (CWE-401) affects the Linux display driver across the GeForce, RTX/Quadro/NVS and Tesla product lines, including vGPU guest-driver and Virtual GPU Manager deployments, and is local-only, requiring an existing low-privileged account (AV:L/PR:L) with no user interaction and causing availability-only impact (C:N/I:N/A:H). No public exploit code and no CISA KEV entry were identified at time of analysis, so exploitation requires an attacker who already holds a shell on the box and can sustain repeated triggering; the practical risk concentrates on shared, multi-tenant GPU hosts (vGPU, VDI, cloud GPU) where one tenant's resource exhaustion degrades every other workload on the same kernel.
Local denial of service in the NVIDIA GPU Display Driver for Linux lets any unprivileged user on the host trigger a NULL pointer dereference (CWE-476) inside the driver's kernel-mode layer, crashing or destabilising the graphics kernel component (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base score 5.5). The flaw spans NVIDIA's GeForce, RTX/Quadro/NVS and Tesla product lines and is bounded strictly to availability impact - there is no confidentiality or integrity loss and no path to privilege escalation - so the practical blast radius is limited to disrupting the machine, and is materially more serious only on multi-tenant or shared-GPU hosts (VDI, cloud GPU) where one low-privilege user's crash affects other tenants. Exploitation requires local access with a normal, non-privileged account and direct interaction with the driver's kernel interface; no public exploit identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV).
Local attackers with low-privileged access can read uninitialized kernel memory from NVIDIA GPU Display Drivers on Windows and Linux, leading to information disclosure. The flaw resides in the kernel-mode driver and requires an existing account on the target system (CVSS 3.1: AV:L/PR:L, 5.5 Medium). No public exploit code or active exploitation has been identified at time of analysis.
NULL pointer dereference in the NVIDIA GPU Display Driver kernel module for Linux allows an authenticated local attacker to crash the driver, resulting in denial of service. Affected products include GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver (vGPU) product lines. Exploitation requires an unprivileged local account (CVSS vector AV:L/PR:L) and yields only denial of service with no confidentiality or integrity impact; no public exploit has been identified at time of analysis.
Denial of service in NVIDIA Display Driver on Windows and Linux allows a local low-privileged attacker to crash the kernel-mode driver by triggering a divide-by-zero condition. Affected product branches include GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager builds prior to the fixed versions in NVIDIA bulletin 5861, with impact limited to availability and no public exploit identified at time of analysis.
Local denial of service in NVIDIA GPU Display Driver for Linux lets a logged-in user or a low-privileged process with GPU device access (PR:L, confirmed via CVSS vector) crash the kernel mode driver by submitting a crafted ioctl that triggers a NULL pointer dereference (CWE-476), rated CVSS 5.5 Medium. Impact is availability-only - the assessed vector shows C:N/I:N/A:H, so no privilege escalation, code execution, or data exposure is achievable, and the attack is strictly local, not remotely reachable. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied for this CVE.
Denial of service in NVIDIA GPU Display Driver for Windows arises from excessive kernel stack consumption in the kernel-mode color transform path when evaluating YCbCr420 display emulation, leading to a stack-based buffer overflow (CWE-121). A local attacker with low privileges (PR:L per the CVSS vector) can crash the system, but there is no impact to confidentiality or integrity. No public exploit code or active exploitation has been identified at time of analysis, and the moderate CVSS 5.5 reflects the local, DoS-only nature, making this a low-priority issue.
Denial of service in the NVIDIA GPU Display Driver for Windows and Linux arises from improper access control (CWE-862) in the kernel-mode layer, where a local user with a low-privileged account can invoke a driver interface they should not be authorized to reach and thereby crash or hang the affected system. Impact is limited to availability: with the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (base 5.5, Medium), exploitation requires pre-existing local authenticated access on a host running an affected driver branch - GeForce, RTX/Quadro/NVS, Tesla, or the vGPU Guest Driver/Virtual GPU Manager - and no remote path exists. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing), and no code execution, privilege escalation, or data disclosure is achievable, making this a low-to-moderate operational priority that is chiefly relevant to multi-user, VDI, and shared-workstation environments.
Privilege escalation and potential code execution in the NVIDIA GPU Display Driver for Windows and Linux arise from an incorrect permission assignment (CWE-732) within a secure microcontroller component, allowing an attacker who already holds privileged local access to write to protected memory that should be restricted. Exploitation is gated by two strong prerequisites - the CVSS vector (AV:L/AC:H/PR:H/UI:N) requires local access with administrator/root-equivalent privileges and high attack complexity - so this is a genuine but lower-tier risk that primarily matters as a post-compromise escalation or persistence primitive rather than a standalone entry vector. Affected branches include GeForce (only Maxwell, Volta, and Pascal architecture GPUs), RTX/Quadro/NVS, and Tesla data-center drivers below the branch-specific fixed versions in NVIDIA bulletin 5861; there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
Use-after-free in the NVIDIA GPU Display Driver kernel module (CVE-2026-47586) allows an attacker with local access to the GPU device on Windows or Linux to corrupt kernel memory, with potential outcomes including code execution, privilege escalation, denial of service, information disclosure, and data tampering. The vendor CVSS vector (AV:P/AC:H/PR:N) is anomalous - designating physical access and no privileges - while the independent assessment uses AV:L/AC:H/PR:L, indicating that exploitation is not remotely triggerable and instead depends on winning a timing/command-sequence race after obtaining local low-privileged access to the driver. No public exploit code or confirmed active exploitation is identified at time of analysis, and exploitation signals point to a low-to-moderate real-world priority despite the memory-corruption impact.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux can be triggered by an already-privileged local user who wins a narrow race condition between concurrent kernel operations, potentially yielding code execution in kernel context, denial of service, privilege escalation, information disclosure, and data tampering. Affected branches include GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver products on Linux (CVSS 3.1 base 6.4). Impact is bounded by the requirement for high local privileges (PR:H) and the non-deterministic nature of the race (AC:H); no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local privilege escalation, code execution, denial of service, information disclosure, and data tampering are possible in NVIDIA GPU Display Driver for Linux due to a use-after-free in the open-source kernel module's event-delivery path. An authenticated local user with access to NVIDIA GPU device nodes can race asynchronous event delivery against file close (CVSS 7.0, AV:L/AC:H/PR:L/UI:N), though the high attack complexity makes success non-deterministic and typically requires repeated attempts; no public exploit has been identified at time of analysis. Risk is concentrated on Linux hosts using the affected open-source kernel module, particularly multi-tenant vGPU, VDI, and cloud GPU deployments.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Out-of-bounds write in the NVIDIA GPU Display Driver for Windows kernel module can let a local, authenticated low-privileged user execute code, escalate privileges, cause denial of service, disclose information, or tamper with data on affected GeForce, RTX/Quadro/NVS, and Tesla systems. Exploitation requires local access to the GPU-equipped Windows host plus a low-privileged account able to reach the kernel module, and the high attack complexity means it is not reliably one-shot; multi-user, VDI, and cloud/virtual-GPU environments are the main risk. No public exploit identified at time of analysis, and CVSS is 7.0 with high confidentiality, integrity, and availability impact.
Denial of service and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.
An out-of-bounds read in the NVIDIA Display Driver for Windows kernel module allows local attackers to cause denial of service and disclose sensitive kernel memory. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver lines on Windows; exploitation requires local access with no elevated privileges or user interaction. No public exploit code has been identified, and the vulnerability is not remotely exploitable.
Authenticated low-privileged local users can bypass cryptographic signature verification in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux when the system is under memory pressure, leading to data tampering and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver branches on Linux; no public exploit code has been identified at time of analysis. Our assessment rates this as a genuine but bounded-priority local issue because the attacker must reliably induce a low-memory kernel state at the moment of verification, making exploitation opportunistic rather than dependable.
Information disclosure and data tampering can be achieved by a local low-privileged attacker exploiting a missing authorization check in the NVIDIA GPU Display Driver for Windows kernel module. Affected products include the GeForce, RTX/Quadro/NVS, and Tesla driver branches on Windows; exploitation requires local authenticated access (PR:L) and no user interaction (UI:N). No public exploit code or active exploitation has been identified at time of analysis; the CVSS score is 7.3 with scope change (S:C) that amplifies risk in multi-user or cloud-GPU environments.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux can be achieved by an unprivileged local user through the open-source kernel module's DMA-BUF import path, where importing a read-only buffer from another device's DMA-BUF exporter improperly preserves memory access permissions. Successful exploitation can result in code execution, privilege escalation, denial of service, information disclosure, and data tampering, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, and no CISA KEV entry is present in the provided data.
Local privilege escalation and kernel-level code execution in the NVIDIA GPU Display Driver for Windows and Linux, where the kernel-mode layer follows an error-handling path that operates on an improperly initialized resource (CWE-908). The flaw is reachable by an authenticated, low-privileged local user (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) on any host where the affected driver is installed and loaded, granting full confidentiality, integrity, and availability impact within the kernel-mode driver's scope. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); risk is concentrated on shared multi-tenant GPU hosts such as VDI, cloud GPU instances, and vGPU guests where untrusted local users coexist with the driver, and success may be probabilistic because the attacker must reliably trigger the failing error path.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in the NVIDIA GPU Display Driver's open-source kernel module lets an unprivileged local user trigger a use-after-free in the Resource Server map cleanup path via a missing self-reference guard, yielding code execution, privilege escalation, denial of service, information disclosure and data tampering (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, CWE-416). Affected are Windows and Linux hosts running the open-source kernel module variant of the driver, spanning GeForce, RTX/Quadro/NVS and Tesla product lines per the published CPEs; exploitation requires only a normal local account and no user interaction, but is strictly local with no network vector. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical risk is highest in shared or multi-tenant GPU environments (vGPU, VDI, cloud GPU) where gaining kernel-level control of the GPU driver crosses a meaningful tenant boundary.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a use-after-free (CWE-416) reachable by a low-privileged local user who can issue a crafted sequence of driver commands. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high, with the greatest risk in shared or virtualized GPU deployments where guest-driver or virtual GPU manager isolation may be broken. No public exploit code or confirmed active exploitation is identified in the available data, and EPSS is not provided; exploitation requires local access and construction of the specific command sequence.
Local privilege escalation in NVIDIA Display Driver for Windows allows an authenticated low-privileged user to trigger a stack-based out-of-bounds write in the kernel mode layer, potentially leading to code execution, privilege escalation, and denial of service. Affected systems include Windows hosts with GeForce, RTX/Quadro/NVS, or Tesla drivers, as well as the Guest Driver in virtualized deployments. No public exploit code or active exploitation has been identified at time of analysis, and the flaw requires local access, making it most relevant to shared multi-tenant environments.
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authenticated unprivileged user to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPUs, as well as Guest Driver and vGPU Manager deployments. With a CVSS score of 7.8, the vulnerability requires local access and low privileges (CVSS vector AV:L/AC:L/PR:L/UI:N), making it primarily a risk in multi-user or shared-GPU environments; no public exploit has been identified at time of analysis, and patched driver branches are available in NVIDIA security bulletin 5861.
Local privilege escalation in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows an unprivileged local user to bypass read-only memory protection and gain write access to memory the driver marked read-only, which can result in kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering. Exploitation requires the attacker to already hold low-privileged local access on an affected Linux host (CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N, score 7.8) with no user interaction and no network vector; the risk is greatest on shared, multi-tenant vGPU, VDI, and cloud-GPU hosts where crossing the user-to-kernel boundary breaks tenant isolation. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but NVIDIA has published a fix through security bulletin 5861. This is a genuine local privilege-escalation risk rather than an emergency, and it should be prioritized on multi-tenant GPU infrastructure.
Local privilege escalation in NVIDIA Display Driver for Windows and Linux allows an unprivileged local attacker to trigger a use-after-free condition by issuing a crafted sequence of driver commands, potentially achieving code execution, privilege escalation, denial of service, or information disclosure. The vulnerability affects systems with GeForce, RTX/Quadro/NVS, or Tesla GPUs running vulnerable driver versions. No public exploit identified at time of analysis.
Local privilege escalation and memory corruption in NVIDIA GPU Display Driver on Windows and Linux, affecting GeForce, RTX/Quadro/NVS, and Tesla lines. An unprivileged local user can trigger a use-after-free (CWE-416) by issuing a specific sequence of driver commands, leading to potential code execution, privilege escalation, denial of service, or information disclosure. Requires local access and low privileges (AV:L/PR:L) with no user interaction (UI:N); no public exploit identified at time of analysis. Risk is highest in multi-user or shared-GPU environments such as VDI, terminal servers, and cloud/virtualized GPU hosts.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, unprivileged user to trigger a use-after-free condition by issuing a specific sequence of driver commands, potentially leading to code execution, privilege escalation, denial of service, and information disclosure. The vulnerability affects GeForce, RTX/Quadro/NVS, and Tesla GPU drivers, including guest-VM vGPU deployments, and requires local access with low privileges. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Use-after-free in the NVIDIA GPU Display Driver for Linux allows a local, unprivileged user to corrupt driver memory by racing or abusing object lifetime handling, with a successful exploit potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The flaw scores 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is confined to local attackers who already hold an account on the GPU host, with no network vector and no user interaction required. This is a genuine but not emergency-grade issue: no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so realistic exposure is concentrated on shared or multi-tenant GPU systems - VDI desktops, cloud GPU instances, and HPC nodes - where untrusted users share a single driver instance.
An integer underflow (CWE-191) in the kernel-mode component of the NVIDIA GPU Display Driver for Windows lets a local, authenticated low-privileged user corrupt kernel memory in a way that can lead to code execution, privilege escalation, denial of service, information disclosure, or data tampering (CVSS 3.1: 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The issue affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches and is not network-reachable, so an attacker must already be able to run code as a normal user on the host. There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is concentrated on multi-user, VDI and cloud-GPU hosts where an unprivileged tenant shares the same machine as the vulnerable driver, while single-user desktops where the attacker must already hold a foothold face lower marginal risk.
Type confusion in the kernel-mode component of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution to corrupt kernel memory and potentially escalate to SYSTEM, crash the machine (BSOD/DoS), disclose kernel memory, or tamper with data. The issue is rated CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning the attacker must be local and authenticated with low privileges and no user interaction is required, and it affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is an access-gated local privilege-escalation risk rather than a remotely reachable mass-exploitation threat.
Local privilege escalation in NVIDIA Display Driver on Windows allows an authenticated low-privileged user to trigger a use-after-free in the kernel-mode driver, potentially enabling code execution with SYSTEM privileges, denial of service, information disclosure, or data tampering. The vulnerability requires local access and high attack complexity (AC:H) due to race conditions or kernel-pool reclamation, making reliable exploitation non-trivial, and it is not known to be actively exploited. The highest risk is in shared multi-user, VDI, or cloud-GPU environments where crossing a trust boundary from low-privileged user to kernel is significant.
Incorrect buffer size calculation in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution on the host to escalate to kernel-level privileges, with downstream risk of code execution, denial of service, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla data-center, and vGPU/Virtual GPU Manager drivers, and rates CVSS 3.1 base 7.8 (AV:L/AC:L/PR:L/UI:N) - it is strictly local, not remotely triggerable, so exposure is limited to shared workstations, multi-tenant vGPU/VDI environments, and cloud-GPU nodes where an untrusted party can already run code. No public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows allows an authenticated attacker with low-privileged code execution to exploit an integer overflow (CWE-190) in the kernel module, potentially achieving code execution, denial of service, information disclosure, and data tampering. The flaw requires local access (AV:L) and low privileges (PR:L) with no user interaction, affecting systems with GeForce, RTX/Quadro/NVS, or Tesla drivers. No public exploit code or active exploitation has been identified at the time of analysis; the CVSS 3.1 base score is 7.8 (HIGH).
Local code execution and denial of service on Windows systems with affected NVIDIA GPU Display Drivers stem from an integer overflow in the display driver's DIAG escape handler that results in an out-of-bounds write (CWE-787). An unprivileged local user (CVSS PR:L) can trigger the flaw via a device I/O call to the handler; no user interaction is required, and exploitation is confined to the local machine, meaning an attacker must already have a foothold. No public exploit identified at time of analysis (and no CISA KEV entry), but the shared-system impact-multi-user workstations, VDI, and cloud GPU instances-raises the risk profile.
An out-of-bounds write in NVIDIA NVAPI for Windows allows a locally authenticated attacker holding standard user privileges to corrupt memory by invoking NVAPI entry points, potentially leading to code execution, elevation of privileges, information disclosure, denial of service, or data tampering. The flaw affects hosts running the NVIDIA GPU driver package on Windows - including GeForce, RTX/Quadro/NVS, and Tesla driver-equipped systems - with a CVSS 3.1 base score of 7.8 (HIGH) under vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. No public exploit code and no confirmed active exploitation (CISA KEV) have been identified at time of analysis, but the local-only, low-privilege prerequisite makes shared and multi-tenant GPU/VDI hosts the most exposed environment.
Type confusion in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a local low-privileged user (CVSS vector AV:L/AC:L/PR:L/UI:N) who can reach the driver's device-node/ioctl interface to trigger memory corruption with high impact across confidentiality, integrity, and availability, potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The CVSS 3.1 base score of 7.8 reflects a local attack vector paired with uniformly high impacts rather than any remote reachability, and despite the 'RCE' tag in the source metadata the vulnerability is not remotely exploitable. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and no EPSS or CISA KEV signal was provided.
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
Local privilege escalation in NVIDIA GPU Display Driver for Windows (CUDA driver component) allows an authenticated attacker with low privileges to execute arbitrary code by planting a malicious library in an uncontrolled search path. Affected products include GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest driver branches. No public exploit identified at time of analysis; exploitation requires local access and write permissions to a directory resolved by the driver's search path, making it most relevant on shared multi-user or VDI/cloud-GPU hosts.
A type-confusion flaw in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux lets a local, low-privileged user who can open the driver's device nodes and issue ioctls trigger memory corruption by winning a handle-recycle race, yielding kernel-level code execution, privilege escalation, denial of service, information disclosure and data tampering. Affected platforms are the Linux driver branches covering GeForce, RTX/Quadro/NVS, Tesla/data-center GPUs and the vGPU guest driver and Virtual GPU Manager (CVSS 3.1 base 7.8; our independent assessment rates it AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, i.e. 7.0, because the race window makes exploitation timing-sensitive rather than deterministic). This is a local privilege-escalation-class issue with no remote vector: no public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), though it is most consequential on multi-user, VDI and cloud/virtualized GPU hosts where untrusted tenants share a single driver instance.
A NULL pointer dereference in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a locally present, low-privileged authenticated user to crash the driver - and potentially the kernel - by supplying a crafted request to the kernel-mode driver layer (for example via device ioctls). Affected platforms span the GeForce, RTX/Quadro/NVS, and Tesla driver lines on Linux, and the 'Guest Driver' / 'Virtual GPU Manager' tags indicate the vGPU path is also in scope, so a guest session inside a virtualized vGPU deployment is a valid attack position. The vendor claims the flaw 'might' lead to code execution, privilege escalation, information disclosure, and data tampering, but the reliably achievable outcome is a denial-of-service crash; there is no CISA KEV listing, no EPSS score provided, and no public exploit identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to trigger an out-of-bounds write in kernel memory via a crafted ioctl call with an unvalidated buffer size, enabling code execution, privilege escalation, information disclosure, and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla drivers, as well as Guest Driver and Virtual GPU Manager components, with highest risk in multi-tenant GPU environments such as VDI and cloud/HPC deployments. No public exploit identified at time of analysis; CVSS 3.1 score is 7.8 (local, low privileges, no user interaction).
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated unprivileged user to trigger a use-after-free in the kernel mode layer, potentially achieving code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw is reachable only by a locally authenticated low-privileged account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) that can issue ioctls to the GPU kernel-mode device interface; there is no remote attack path and no user interaction is required once a foothold exists. The 'Guest Driver' classification makes the issue most consequential in virtualized/vGPU and multi-tenant datacenter environments, where a low-privileged guest can reach the shared GPU driver. No public exploit identified at time of analysis, and the vendor advisory is the authoritative source for fixed driver versions.
Local privilege escalation in NVIDIA's GPU Display Driver (GeForce, RTX/Quadro/NVS, and Tesla, on both Windows and Linux) allows an authenticated low-privileged local user to reach GPU memory belonging to another process, enabling code execution, escalation of privileges, data tampering, denial of service, and information disclosure. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) there is no remote or network path; the flaw is most consequential on shared, multi-user, VDI, or multi-tenant GPU hosts where cross-process GPU memory isolation is the boundary between users and tenants. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the provided vendor reference points to NVIDIA's product security advisory (2026/5861) rather than a fixed driver version named in this data set.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel mode layer allows an authenticated, unprivileged user to trigger a double-free of imported memory state, potentially leading to code execution, denial of service, information disclosure, and data tampering. The flaw requires local access and a low-privilege account; no public exploit code or active exploitation has been identified at time of analysis. The CVSS 3.1 score is 7.8 (HIGH).
Local privilege escalation, code execution, denial of service, and information disclosure in NVIDIA GPU Display Driver on Windows and Linux stem from an integer overflow (CWE-190) in the kernel-mode layer that an unprivileged user can trigger to cause an out-of-bounds write. Exploitation requires local access with an existing low-privilege account (authenticated, PR:L) on a host with an affected GeForce, RTX/Quadro/NVS, or Tesla driver; the CVSS v3.1 base score is 7.8 (High) with a local attack vector (AV:L/AC:L/PR:L/UI:N). No public exploit code or CISA KEV entry was identified at the time of analysis, but the flaw is genuine and actionable for local privilege escalation if the vulnerable driver interface is reachable.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows an unprivileged local user to corrupt kernel memory, which can lead to code execution in the kernel, privilege escalation, denial of service, information disclosure, or data tampering. Systems running GeForce, RTX/Quadro/NVS, or Tesla driver packages on either operating system are affected; per the CVSS vector (AV:L, PR:L, UI:N) the flaw is reachable only by a user who already has local code execution on the host, making it a local privilege-escalation primitive rather than a remote entry point. No public exploit has been identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux stems from a missing authorization check in the kernel mode layer, allowing an unprivileged local user to modify privileged configuration and potentially achieve code execution, escalation of privileges, denial of service, information disclosure, and data tampering. Exploitation requires a pre-existing local low-privileged foothold (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), such as an unprivileged account on a host or inside a guest VM using the NVIDIA guest driver or Virtual GPU Manager, so this is an escalation primitive rather than a remote initial-access vector. No public exploit code is identified and no CISA KEV active exploitation is confirmed at time of analysis, but the high confidentiality, integrity, and availability impacts and broad affected driver families make patching a priority.
Use-after-free in the NVIDIA GPU Display Driver kernel mode layer (Windows and Linux) lets a local user who already holds low-privileged code execution on the host trigger a memory-corruption condition inside the kernel driver, with the potential for code execution, privilege escalation, information disclosure, data tampering, and denial of service. Affected platforms span consumer and professional GPU lines (GeForce, RTX/Quadro/NVS, Tesla) as well as the vGPU components, where a malicious or compromised guest can exercise the vulnerable path through the Guest Driver and Virtual GPU Manager. The attack is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, score 7.8), requires no user interaction and no non-default configuration beyond having the driver installed, and there is no public exploit identified at time of analysis - no KEV entry and no proof-of-concept code is referenced in the available data.
Local privilege escalation in NVIDIA GPU Display Drivers for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU) allows an unprivileged local user to execute code in kernel mode by supplying an untrusted pointer that the driver dereferences without validation. Affected hosts include multi-user and virtualized Windows systems with default driver installations, where exploitation can lead to escalation to SYSTEM, denial of service, information disclosure, and data tampering. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; the CVSS 3.1 base score is 7.8 (High).
A locally-triggered out-of-bounds write in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-level privileges on a Windows or Linux host corrupt kernel memory, with the potential for code execution in kernel context, escalation of privileges, denial of service, information disclosure and data tampering. The affected driver ships by default across the GeForce, RTX/Quadro/NVS, Tesla and Virtual GPU Manager product lines, so any host with a current NVIDIA driver installed is in scope, but exploitation is not remote: an attacker must first obtain code execution on the target (an authenticated local user, a compromised low-privileged process, or sandboxed code with driver access) and then develop a reliable kernel corruption exploit. CVE-2026-47548 carries a vendor/NVD CVSS 3.1 vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8, High); no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Local attackers with low-privileged code execution can trigger an out-of-bounds read (CWE-125) in the kernel-mode layer of the NVIDIA GPU Display Driver on Windows and Linux, which may lead to escalation of privileges, code execution, denial of service, information disclosure, and data tampering. This locally exploitable flaw (CVSS 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) affects GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager products, and no public exploit has been identified at the time of analysis. A vendor advisory with remediation guidance is available from NVIDIA via its product security page.
Integer underflow in the kernel-mode layer of NVIDIA GPU Display Driver for Windows and Linux allows a local attacker with low privileges to potentially achieve code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Manager products, and exploitation requires local access (CVSS AV:L) with no user interaction (UI:N) but low privileges (PR:L). No public exploit code has been identified at time of analysis, and there is no indication of active exploitation.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged authenticated user to corrupt kernel memory, with the potential to escalate privileges to kernel-level code execution, crash the system (denial of service), disclose information, or tamper with data. The flaw rates CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires pre-existing code execution as a standard user on a host with the driver loaded, but no user interaction and no non-default configuration; the vulnerable kernel-mode layer ships and loads by default once the driver is installed. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, but the affected GeForce, RTX/Quadro/NVS, and Tesla product families are extremely widely deployed, making this a genuine high-priority patch-management item rather than an emergency.
Local attackers with low privileges can exploit an uninitialized pointer access flaw (CWE-824) in the firmware of NVIDIA Display Driver for Windows and Linux to achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering. The vulnerability requires local access (AV:L) and authenticated low-privilege credentials (PR:L); no public exploit identified at time of analysis. Affected products include GeForce, RTX/Quadro/NVS, and Tesla product lines, including vGPU Manager deployments.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds low-privilege code execution corrupt kernel memory, with potential outcomes of privilege escalation, arbitrary code execution, denial of service, information disclosure and data tampering (CWE-787, CVSS 7.8). The assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H shows low attack complexity and no user interaction, but the attack is strictly local: an attacker must first have a foothold on the host, or on a guest in a vGPU configuration, which confines it to privilege-escalation and sandbox-escape scenarios rather than remote mass exploitation. No public exploit code and no confirmed active exploitation were identified at time of analysis (no public exploit identified at time of analysis), so this is a genuine local privilege-escalation priority despite the absence of exploitation signals, and it warrants prompt patching on endpoint, workstation, and multi-tenant virtual-desktop estates.
A use-after-free (CWE-416) in the NVIDIA GPU Display Driver for Windows and Linux lets a local unprivileged user free and then re-reference a driver-managed memory object, potentially yielding code execution in kernel context, privilege escalation, data tampering, denial of service, and information disclosure. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and affects GeForce, RTX/Quadro/NVS, and Tesla product lines; the 'Guest Driver' tag indicates the vulnerable path may also be reachable from inside a virtualized guest, making guest-to-host or guest-context escalation a relevant scenario. Exploitation requires that the attacker already hold a local foothold with normal user privileges on a host with the affected driver installed and the GPU device interface exposed - there is no remote/network vector - and at time of analysis no public exploit code and no confirmed active exploitation have been identified, so this is a priority local privilege-escalation issue rather than an imminent, opportunistically exploited threat.
Local kernel stack memory disclosure in NVIDIA GPU Display Driver for Windows and Linux allows an attacker who already has low-privilege authenticated code execution on the host to read kernel stack contents such as return addresses and pointers. Affected installations include GeForce, RTX/Quadro/NVS, and Tesla driver configurations, and the independent assessment rates the flaw as AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning high confidentiality impact without confirmed integrity or availability impact. No public exploit is identified at time of analysis, and no CISA KEV active exploitation is reported.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged user to read beyond the bounds of kernel heap memory, producing information disclosure and denial of service, with potential for privilege escalation, code execution, and data tampering if the read primitive is successfully leveraged. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla product families on systems with the vulnerable driver branch installed, and exploitation requires an attacker to already hold local access to the host (per the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N vector, base 7.8), with no user interaction needed. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so exploitation is currently expected to require a motivated local attacker rather than being broadly weaponized.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds a low-privileged execution context on the host read past the bounds of a kernel buffer, exposing kernel memory contents and creating a pathway toward further privilege escalation or data tampering. Exploitation is constrained to the local attack surface: the attacker must already be able to run code on the machine (AV:L, PR:L) and no user interaction or network path is involved, so despite the 7.8 headline score the practical risk is a local privilege/information-disclosure concern rather than a remotely reachable, mass-exploitable flaw. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the affected hardware spans GeForce, RTX/Quadro/NVS, and Tesla products, with an NVIDIA vendor advisory available.
Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer allows a user with standard privileges to trigger an out-of-bounds write in kernel memory, potentially achieving kernel-level code execution, denial of service, information disclosure and data tampering. The affected driver branches span NVIDIA GeForce, RTX/Quadro/NVS and Tesla families on both Windows and Linux, and the 'Guest Driver' tag indicates virtualized/vGPU and guest-VM driver deployments are also in scope, which matters for GPU-accelerated VDI and datacenter estates. Exploitation is constrained to the host: the CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), so an attacker must already have a foothold and the ability to run code as a low-privileged local user; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged local user to trigger an integer overflow in the kernel mode layer, resulting in an out-of-bounds write to GPU memory that can lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. Affected platforms include GeForce, RTX/Quadro/NVS, and Tesla drivers, with the 'Guest Driver' tag indicating that VM guests with GPU access are also in scope for guest-to-host or in-guest escalation. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and the CVSS 3.1 score is 7.8 (AV:L/PR:L/UI:N).
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged user to trigger an incorrect conversion between numeric types in the kernel mode layer, potentially leading to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The vulnerability requires local access and low-level privileges (CVSS vector PR:L) with no user interaction, and it is not remotely exploitable. No public exploit code has been identified at time of analysis, but the risk is materially higher on shared or multi-tenant GPU hosts such as VDI, vGPU, or Tesla datacenter deployments where untrusted users can reach the driver.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows and Linux lets a low-privileged local user trigger an out-of-bounds array access in the kernel mode layer, potentially yielding code execution in kernel context, denial of service, escalation of privileges, information disclosure and data tampering. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), meaning the attack is strictly local and requires only low-privileged authenticated code on the host, with no user interaction and low complexity - so any unprivileged process able to reach the affected kernel-mode interface on a system running GeForce, RTX/Quadro/NVS or Tesla drivers (or a vGPU host reachable from a guest) can attempt it. There is confirmed actively exploited (CISA KEV) status: no - the CVE is not in KEV and no public exploit code has been identified at time of analysis, so early patching is key while exploitation activity has not yet been observed.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows allows a low-privileged local user - or a sandboxed process or guest with access to the driver interface - to trigger a use-after-free in the kernel-mode layer, potentially achieving kernel code execution, privilege escalation, denial of service, information disclosure, or data tampering. The assessed vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) means the attacker must already have code running on a host with an affected NVIDIA driver installed, but needs no user interaction and faces low complexity once local access exists; per the affected CPEs, the GeForce, RTX/Quadro/NVS, and Tesla branches are in scope, and the associated Guest Driver and Virtual GPU Manager tags mean a virtual-GPU guest may also be able to reach the kernel layer. No public exploit code or confirmed active exploitation was identified at the time of analysis, and hosts without an NVIDIA GPU/driver installed are unaffected.
Local code execution, privilege escalation, denial of service, information disclosure, and data tampering are possible on Linux systems running vulnerable NVIDIA GPU Display Drivers (GeForce, RTX/Quadro/NVS, and Tesla branches) because of a type-confusion flaw (CWE-843) in the outdated embedded cryptographic library used by the NGX updater. The assessed profile is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8): an attacker who already holds a low-privileged local account can reach the vulnerable updater code path, with no user interaction required and low complexity, but the flaw is not remotely reachable, so shared and multi-user hosts (VDI, HPC/Tesla compute clusters, and workstations with untrusted local users) are the realistic risk surface. No public exploit code has been identified at time of analysis, and the exact affected and fixed driver versions must be confirmed from NVIDIA's advisory.
Integer overflow in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager can be triggered by a low-privileged user inside a guest VM, causing memory corruption with high confidentiality, integrity, and availability impact. The vulnerability affects vGPU deployments on Windows and Linux hosts across GeForce, RTX/Quadro/NVS, and Tesla driver branches, and successful exploitation could enable code execution, denial of service, privilege escalation, information disclosure, or data tampering. No public exploit code or active exploitation has been identified in the provided intelligence at time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, low-privileged user to drive an out-of-bounds write in the driver's kernel-mode layer by supplying mismatched memory buffers during event buffer setup, with a successful exploit potentially leading to kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The affected code is the Linux kernel-mode component shipped with GeForce, RTX/Quadro/NVS and Tesla driver packages, and the same path can be reached by untrusted code inside a guest VM using the NVIDIA vGPU guest driver on a host running the Virtual GPU Manager. No public exploit code was identified and there is no confirmed active exploitation (CISA KEV) at time of analysis; the bug is local-only, requiring the attacker to already run code with at least low privileges on the host or in a guest, and it is not remotely reachable.
Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-privileged code execution on a Windows or Linux host - including code running inside a vGPU guest VM - drive the driver into an error path that mishandles reference counts, producing a use-after-free. The corrupted object is kernel memory, so successful exploitation can yield code execution, escalation of privileges, denial of service, information disclosure, and data tampering (CVSS 7.8, AV:L/AC:L/PR:L/UI:N); it is not remotely reachable and requires a vulnerable driver version to be installed. The GeForce, RTX/Quadro/NVS, and Tesla driver families are in scope, and no public exploit code has been identified at the time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux lets an already-authenticated, low-privileged user trigger a format string defect (CWE-134) and potentially achieve code execution, privilege escalation, data tampering, denial of service, and information disclosure; NVIDIA rates it 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack surface is strictly local - there is no remote vector - so real risk concentrates on multi-user and multi-tenant GPU systems such as HPC clusters, ML/AI training nodes, shared engineering workstations, and cloud GPU instances, where a low-privileged tenant could reach the driver while other users' data and the host remain in scope. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; the impact rating of total confidentiality, integrity, and availability loss is consistent with memory corruption inside a privileged driver context.
Local privilege escalation and kernel memory-safety compromise on Linux systems running NVIDIA GPU Display Drivers allow an unprivileged local user to cause improper release of kernel-mode memory resources, leaving a mapping accessible after the underlying memory has been reused. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver lines and carries a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning an attacker who already holds a local login can potentially achieve code execution, denial of service, information disclosure, privilege escalation, and data tampering without user interaction. No public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited, but the local-only vector makes it most dangerous on shared or multi-tenant GPU hosts where one unprivileged tenant could compromise the kernel and other workloads.
Local privilege escalation and memory-protection bypass in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to execute code at higher privilege, tamper with data, disclose information, or cause denial of service. The flaw is in the kernel-mode layer and affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver/Virtual GPU Manager deployments, with a CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N). No public exploit identified at time of analysis, and no CISA KEV active-exploitation signal is present; the assessed attack path requires prior local access on the host or inside a vGPU guest.
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest drivers) allows an authenticated local user to abuse improper permission handling in a kernel mode layer handler, enabling code execution, privilege elevation, and data tampering. CVSS 7.8 reflects high impact across confidentiality, integrity, and availability, but the attack vector is local and authenticated. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC marks technical impact as total.
Local privilege escalation in NVIDIA Display Driver for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest/manager components) stems from a time-of-check time-of-use (TOCTOU) race condition that can be abused by a low-privileged local user. Successful exploitation may yield code execution, privilege escalation, denial of service, information disclosure, or data tampering with scope change beyond the driver's security boundary. No public exploit identified at time of analysis; EPSS is 0.01% and SSVC exploitation status is 'none', so the practical risk is contingent on local access and winning a high-complexity race.
Local privilege escalation in NVIDIA Display Driver for Windows and Linux allows authenticated low-privilege users to improperly access GPU resources via a kernel mode layer flaw, potentially leading to code execution, privilege escalation, information disclosure, data tampering, and denial of service. The issue affects GeForce, RTX/Quadro/NVS, and Tesla product lines across multiple driver branches and carries a CVSS 7.8 (High) score. No public exploit identified at time of analysis, and EPSS probability is very low (0.01%), but the breadth of affected hardware and total technical impact warrant prompt patching.
Local privilege escalation in the NVIDIA Display Driver for Windows and Linux allows an authenticated low-privileged user to trigger an out-of-bounds write (CWE-787) in the kernel-mode driver, potentially leading to code execution, privilege escalation, information disclosure, data tampering, or denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla product lines, with NVIDIA confirming the vulnerability and releasing patched driver versions. No public exploit identified at time of analysis, and EPSS rates exploitation probability at just 0.01%.
Out-of-bounds read in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest drivers) allows a locally authenticated user to trigger denial of service and information disclosure. The flaw carries a CVSS 3.1 score of 7.1 (AV:L/AC:L/PR:L), and per CISA SSVC there is no public exploit identified at time of analysis (Exploitation: none), with EPSS at 0.01% indicating negligible near-term exploitation likelihood. NVIDIA has published fixed driver versions across all affected branches in advisory ID 5821.
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager branches) stems from an incorrect numeric type conversion (CWE-681) that produces a heap buffer overflow. A locally authenticated attacker with low privileges can trigger the flaw to achieve code execution, privilege escalation, information disclosure, data tampering, or denial of service. No public exploit identified at time of analysis, and EPSS is very low (0.01%, 1st percentile), but technical impact per SSVC is total.
Local privilege escalation and code execution in the NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest/Manager components) stems from a use-after-free memory corruption flaw (CWE-416) that a local low-privileged user can trigger to compromise the kernel-level driver. The scope-changed CVSS 8.8 score reflects that successful exploitation crosses a trust boundary, potentially yielding code execution, privilege escalation, information disclosure, data tampering, or denial of service. EPSS is 0.01% (1st percentile) and there is no public exploit identified at time of analysis, but a vendor patch is available across all affected branches.
Local attackers with low privileges can inject crafted text into the kernel log on Linux systems running the NVIDIA GPU Display Driver because the kernel mode layer fails to sanitize a supplied version string, leading to denial of service and data tampering. The vulnerability requires local access (AV:L) and low privileges (PR:L) with no user interaction, and has low impact on integrity and availability (I:L/A:L) with no confidentiality loss. No public exploit identified at time of analysis, and the overall risk is low despite the wide deployment of NVIDIA GPUs.
Denial of service in the NVIDIA GPU Display Driver for Windows and Linux occurs when a NULL pointer dereference is triggered in the kernel-mode layer, crashing or hanging the graphics subsystem on the affected host. Only systems with a physical NVIDIA GPU (GeForce, RTX/Quadro/NVS, or Tesla branches) running a driver older than the branch-specific fixed release are exposed, and exploitation requires an attacker who already holds HIGH privileges (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H), so an unprivileged local user cannot reach the vulnerable interface. There is no confidentiality or integrity impact, no public exploit code and no confirmed active exploitation (not in CISA KEV), and the EPSS score was not reported; the high-privilege prerequisite caps real-world priority at LOW despite the nominal MEDIUM CVSS.
Denial of service in NVIDIA GPU Display Driver on Windows and Linux is possible when a highly privileged local attacker reaches a firmware code path that dereferences a null pointer. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver branches prior to the fixes documented in NVIDIA bulletin 5861, with some older branches limited to Maxwell, Volta, and Pascal GPUs. The assessed vector is local and requires high privileges, with availability impact only; no public exploit identified at time of analysis, and the low CVSS score of 4.4 reflects those constraints.
Information disclosure in the NVIDIA GPU Display Driver kernel-mode component (Windows and Linux) lets an authenticated local user read another process's GPU channel state, because the driver performs missing authorization checks (CWE-862) when a process requests channel state it does not own. The flaw is rated CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so it requires a pre-existing local, low-privileged foothold and yields confidentiality impact only - no integrity or availability effect - and there is no public exploit identified at time of analysis. Practical risk concentrates on hosts where multiple security contexts share the same GPU, such as multi-user workstations, VDI, and cloud/virtual-GPU deployments; single-user desktops with one active GPU context gain little from this primitive, so the overall priority is low-to-moderate and locally scoped.
Local information disclosure in NVIDIA Display Driver for Windows and Linux allows an authenticated local user with low privileges to access another process's GPU channel state because the kernel-mode driver omits authorization checks. Affected platforms include NVIDIA GeForce, RTX/Quadro/NVS, and Tesla GPUs; the issue is rated CVSS 5.5 with high confidentiality impact but no integrity or availability impact. No public exploit was identified at time of analysis, and the practical risk is greatest in multi-user or multi-tenant GPU environments such as VDI and cloud-GPU deployments.
A NULL pointer dereference in the kernel-mode component of the NVIDIA GPU Display Driver for Windows allows a local attacker who can already execute low-privileged code on the host to crash the graphics kernel driver, taking down the display stack or bugchecking the whole machine. The flaw is confined to availability: per the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, there is no network path, no user interaction, and no confidentiality or integrity impact, so it cannot be used for code execution, privilege escalation, or data disclosure. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS/KEV signals are absent; the practical risk is concentrated on multi-user, VDI, or cloud-GPU Windows hosts where an unprivileged tenant could repeatedly disrupt the machine, making this a genuinely low-to-moderate priority issue despite the ubiquity of the affected hardware.
Denial of service in the NVIDIA GPU Display Driver for Windows kernel module allows a local low-privileged user to trigger improper locking, potentially crashing or hanging the system. The vulnerability affects GeForce, RTX/Quadro/NVS, and Tesla product lines, but exploitation is limited to local access with existing low-level privileges and no user interaction, resulting in availability impact only. No public exploit code or active exploitation has been identified at time of analysis, and the CVSS score is 5.5, making this a low-to-moderate priority issue despite the ubiquity of the driver.
Local, authenticated, low-privilege users on Linux hosts can cause a denial-of-service condition against the NVIDIA GPU Display Driver kernel-mode layer by repeatedly invoking an interface that emits unrate-limited error messages, leading to uncontrolled kernel log generation and resource exhaustion. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPU families running the Linux driver, as reflected in the NVIDIA CPE entries. Despite the moderate 5.5 CVSS score, this is a low-priority issue because exploitation requires local code execution with no remote or unauthenticated path, only availability is impacted, and no public exploit has been identified at time of analysis.
Denial of service in NVIDIA GPU Display Driver for Linux arises when a local authenticated low-privileged user exhausts the DRM VMA offset address space, causing uncontrolled resource consumption in the kernel mode layer. The issue is limited to Linux and to availability impact; exploitation requires an existing local foothold and cannot provide code execution, privilege escalation, or data disclosure. No public exploit was identified at time of analysis, and the assessed risk is low, though shared or multi-tenant GPU systems such as VDI, cloud GPU, and Tesla/vGPU deployments face the greatest practical disruption.
Kernel memory exhaustion in the NVIDIA GPU Display Driver for Linux allows a local, unprivileged user to repeatedly drive error-handling paths in the driver's kernel-mode layer so that leaked allocations accumulate until kernel memory is depleted, resulting in a denial of service on the affected host. The flaw (CWE-401) affects the Linux display driver across the GeForce, RTX/Quadro/NVS and Tesla product lines, including vGPU guest-driver and Virtual GPU Manager deployments, and is local-only, requiring an existing low-privileged account (AV:L/PR:L) with no user interaction and causing availability-only impact (C:N/I:N/A:H). No public exploit code and no CISA KEV entry were identified at time of analysis, so exploitation requires an attacker who already holds a shell on the box and can sustain repeated triggering; the practical risk concentrates on shared, multi-tenant GPU hosts (vGPU, VDI, cloud GPU) where one tenant's resource exhaustion degrades every other workload on the same kernel.
Local denial of service in the NVIDIA GPU Display Driver for Linux lets any unprivileged user on the host trigger a NULL pointer dereference (CWE-476) inside the driver's kernel-mode layer, crashing or destabilising the graphics kernel component (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base score 5.5). The flaw spans NVIDIA's GeForce, RTX/Quadro/NVS and Tesla product lines and is bounded strictly to availability impact - there is no confidentiality or integrity loss and no path to privilege escalation - so the practical blast radius is limited to disrupting the machine, and is materially more serious only on multi-tenant or shared-GPU hosts (VDI, cloud GPU) where one low-privilege user's crash affects other tenants. Exploitation requires local access with a normal, non-privileged account and direct interaction with the driver's kernel interface; no public exploit identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV).
Local attackers with low-privileged access can read uninitialized kernel memory from NVIDIA GPU Display Drivers on Windows and Linux, leading to information disclosure. The flaw resides in the kernel-mode driver and requires an existing account on the target system (CVSS 3.1: AV:L/PR:L, 5.5 Medium). No public exploit code or active exploitation has been identified at time of analysis.
NULL pointer dereference in the NVIDIA GPU Display Driver kernel module for Linux allows an authenticated local attacker to crash the driver, resulting in denial of service. Affected products include GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver (vGPU) product lines. Exploitation requires an unprivileged local account (CVSS vector AV:L/PR:L) and yields only denial of service with no confidentiality or integrity impact; no public exploit has been identified at time of analysis.
Denial of service in NVIDIA Display Driver on Windows and Linux allows a local low-privileged attacker to crash the kernel-mode driver by triggering a divide-by-zero condition. Affected product branches include GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager builds prior to the fixed versions in NVIDIA bulletin 5861, with impact limited to availability and no public exploit identified at time of analysis.
Local denial of service in NVIDIA GPU Display Driver for Linux lets a logged-in user or a low-privileged process with GPU device access (PR:L, confirmed via CVSS vector) crash the kernel mode driver by submitting a crafted ioctl that triggers a NULL pointer dereference (CWE-476), rated CVSS 5.5 Medium. Impact is availability-only - the assessed vector shows C:N/I:N/A:H, so no privilege escalation, code execution, or data exposure is achievable, and the attack is strictly local, not remotely reachable. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied for this CVE.
Denial of service in NVIDIA GPU Display Driver for Windows arises from excessive kernel stack consumption in the kernel-mode color transform path when evaluating YCbCr420 display emulation, leading to a stack-based buffer overflow (CWE-121). A local attacker with low privileges (PR:L per the CVSS vector) can crash the system, but there is no impact to confidentiality or integrity. No public exploit code or active exploitation has been identified at time of analysis, and the moderate CVSS 5.5 reflects the local, DoS-only nature, making this a low-priority issue.
Denial of service in the NVIDIA GPU Display Driver for Windows and Linux arises from improper access control (CWE-862) in the kernel-mode layer, where a local user with a low-privileged account can invoke a driver interface they should not be authorized to reach and thereby crash or hang the affected system. Impact is limited to availability: with the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (base 5.5, Medium), exploitation requires pre-existing local authenticated access on a host running an affected driver branch - GeForce, RTX/Quadro/NVS, Tesla, or the vGPU Guest Driver/Virtual GPU Manager - and no remote path exists. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing), and no code execution, privilege escalation, or data disclosure is achievable, making this a low-to-moderate operational priority that is chiefly relevant to multi-user, VDI, and shared-workstation environments.
Privilege escalation and potential code execution in the NVIDIA GPU Display Driver for Windows and Linux arise from an incorrect permission assignment (CWE-732) within a secure microcontroller component, allowing an attacker who already holds privileged local access to write to protected memory that should be restricted. Exploitation is gated by two strong prerequisites - the CVSS vector (AV:L/AC:H/PR:H/UI:N) requires local access with administrator/root-equivalent privileges and high attack complexity - so this is a genuine but lower-tier risk that primarily matters as a post-compromise escalation or persistence primitive rather than a standalone entry vector. Affected branches include GeForce (only Maxwell, Volta, and Pascal architecture GPUs), RTX/Quadro/NVS, and Tesla data-center drivers below the branch-specific fixed versions in NVIDIA bulletin 5861; there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
Use-after-free in the NVIDIA GPU Display Driver kernel module (CVE-2026-47586) allows an attacker with local access to the GPU device on Windows or Linux to corrupt kernel memory, with potential outcomes including code execution, privilege escalation, denial of service, information disclosure, and data tampering. The vendor CVSS vector (AV:P/AC:H/PR:N) is anomalous - designating physical access and no privileges - while the independent assessment uses AV:L/AC:H/PR:L, indicating that exploitation is not remotely triggerable and instead depends on winning a timing/command-sequence race after obtaining local low-privileged access to the driver. No public exploit code or confirmed active exploitation is identified at time of analysis, and exploitation signals point to a low-to-moderate real-world priority despite the memory-corruption impact.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux can be triggered by an already-privileged local user who wins a narrow race condition between concurrent kernel operations, potentially yielding code execution in kernel context, denial of service, privilege escalation, information disclosure, and data tampering. Affected branches include GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver products on Linux (CVSS 3.1 base 6.4). Impact is bounded by the requirement for high local privileges (PR:H) and the non-deterministic nature of the race (AC:H); no public exploit code and no confirmed active exploitation were identified at time of analysis.