Virtual Gpu Manager
Monthly
Out-of-bounds write in the NVIDIA Virtual GPU Manager (vGPU plugin) lets an unprivileged user inside an assigned guest VM corrupt host-side memory by sending a specially crafted RPC call across the virtualization channel, resulting in privilege escalation, data tampering, and denial of service on the host. Rated CVSS 7.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H), the bug is only reachable in vGPU/VDI/cloud-GPU deployments where the host runs the vGPU plugin and has at least one guest assigned; it is not a network-facing flaw and does not affect standard bare-metal Linux GPU driver installs, and no public exploit code has been identified at time of analysis. Real-world risk is therefore defined by the attack surface rather than by mass exploitability, since a successful attack requires an attacker to already hold an unprivileged local account inside a hosted guest VM.
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned, low-privileged attacker to break an internal resource-handling boundary and gain high-integrity impact - code execution, privilege escalation, data tampering, information disclosure, or denial of service on the host running the vGPU Manager. This affects virtualization/vGPU deployments on Linux (the manager component on the hypervisor host), not standard desktop GPU drivers, and the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confirms the attacker must already hold local low-privileged access to a context served by that manager, such as a guest VM or a local account on the host; there is no network or unauthenticated path. It is a genuine local privilege-escalation class issue rather than a remotely triggerable one, and no public exploit was identified at time of analysis.
An out-of-bounds write in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker with low privileges corrupt kernel memory, which the vendor rates as potentially leading to code execution, denial of service, privilege escalation, information disclosure, and data tampering (CVSS 3.1 base 7.8, HIGH). The attack is strictly local - vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - so it is not remotely exploitable and requires only an authenticated low-privileged context or a tenant/guest that can reach the host kernel module; the risk is highest in multi-tenant VDI and cloud-GPU deployments where local access is comparatively easy to obtain. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so there is no evidence of confirmed active exploitation.
Local privilege escalation, code execution, denial of service, and information disclosure affect Linux hosts running NVIDIA vGPU Virtual GPU Manager because of an out-of-bounds read in the kernel-mode layer that services vGPU requests. A low-privileged local account or existing code-execution context (CVSS PR:L) is required, and no user interaction is needed, but the flaw is not remotely reachable and only impacts hosts with the vGPU Manager component installed. No public exploit or proof-of-concept has been identified at time of analysis, and EPSS data was not provided; the independent assessment rates this as a moderate, locally-scoped risk.
Local privilege escalation in NVIDIA vGPU Virtual GPU Manager for Linux stems from an out-of-bounds read in firmware (CWE-125) that a low-privileged local attacker can trigger with no user interaction and low complexity. The CVSS 3.1 score is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting high confidentiality, integrity, and availability impact on vGPU/VDI/cloud-GPU hosts that use the affected Linux Virtual GPU Manager. No public exploit was identified at time of analysis, and exploitation requires an existing local foothold; it is not remotely exploitable despite the RCE tag.
Local attackers with low privileges on a Linux host running NVIDIA vGPU Virtual GPU Manager can trigger an out-of-bounds read in the kernel-mode layer, potentially leading to code execution, privilege escalation, denial of service, information disclosure, and data tampering. The flaw is not remotely reachable and affects only virtualization, VDI, or cloud-GPU hosts that run the vGPU Manager. No public exploit code or active exploitation has been identified at time of analysis.
Out-of-bounds read in NVIDIA vGPU Virtual GPU Manager for Linux allows a local authenticated attacker with low privileges to potentially achieve code execution, denial of service, or information disclosure. The vulnerability resides in the kernel-mode driver and affects both the vGPU Manager and guest driver components. No public exploit code has been identified, and the flaw is not known to be actively exploited. Integrity impact is assessed as low, but confidentiality and availability impacts are high, making this a significant risk in multi-tenant vGPU deployments.
An out-of-bounds read in the kernel-mode layer of the NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker who can already reach the vGPU kernel interface trigger memory reads past the bounds of an allocated buffer, potentially yielding information disclosure, data tampering, privilege escalation, denial of service, or kernel code execution. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning it is only reachable by an authenticated local principal - a low-privileged user or a guest context on the hypervisor - and not by an unauthenticated remote network attacker. Exposure is limited to hosts that actually deploy NVIDIA vGPU on Linux (VDI and cloud-GPU virtualization platforms), where the highest-impact scenario is a multi-tenant deployment in which the over-read crosses tenant isolation boundaries; no public exploit code or CISA KEV entry was identified at time of analysis, so this is a genuine but not emergency-grade issue warranting scheduled patching.
An out-of-bounds write in the NVIDIA Virtual GPU Manager (vGPU plugin) for Linux allows a user who already holds a low-privileged account inside a guest VM to corrupt host-side memory by sending a crafted RPC message whose performance-state list size parameters are invalid, potentially yielding code execution, privilege escalation, data tampering, denial of service, or information disclosure across the virtualization boundary. The defect is locally triggered (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) and requires no user interaction, but it is only reachable on hosts actually running the vGPU Manager for multi-tenant vGPU/VDI/cloud-GPU workloads - single-tenant systems without vGPU virtualization are not exposed through this guest-to-host path. No public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV); exploitability is constrained by the need for prior guest authentication and the presence of the vGPU component, making this a contained but genuine virtualization-trust-boundary flaw rather than a broad remote threat.
Out-of-bounds read (CWE-125) in the kernel-mode layer of NVIDIA's vGPU Virtual GPU Manager for Windows and Linux allows a low-privileged process inside a guest VM to force the host-side vGPU driver to read past the end of an allocated buffer (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), primarily exposing host memory contents and creating crash and denial-of-service risk, with code execution and privilege escalation described by the vendor only as possible rather than demonstrated. The issue is reachable only on hosts actively running vGPU configurations such as VDI or cloud GPU hosting where an attacker already holds a foothold inside a guest; bare-metal and non-vGPU installations are not affected, and no user interaction or network reach is required. No public exploit code or confirmed active exploitation has been identified at time of analysis, and no fixed driver version appears in the available intelligence, so defenders should treat patch confirmation through NVIDIA's advisory as the priority action.
An out-of-bounds write in NVIDIA vGPU Manager's GPU System Processor (GSP) plugin lets an authenticated user inside a guest VM hit host-side plugin code with a specially crafted RPC message, potentially yielding code execution, privilege escalation, data tampering, denial of service, or information disclosure in the virtualization host stack. The practical barrier is an existing foothold in an authorized vGPU guest rather than network reachability, and no public exploit code has been identified at time of analysis. Scoring 7.8 under CVSS 3.1 (AV:L/AC:L/PR:L/UI:N, with high confidentiality, integrity, and availability impact) it represents a Moderate, locally-scoped risk that matters most in multi-tenant vGPU deployments where guest-to-host isolation is a core control.
Improper access through a buffer shared between a guest VM and the host in NVIDIA Virtual GPU Manager's GPU System Processor (GSP) tracing component (CWE-367, time-of-check-to-time-of-use) can lead to code execution, privilege escalation, data tampering, denial of service and information disclosure on the affected host. Exploitation is local rather than network-facing: the attacker must already hold user-level code execution inside a vGPU-attached guest VM and must additionally win a timing-dependent race against the host-side tracing path (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H per independent assessment). No public exploit code and no confirmed active exploitation were identified at time of analysis, so practical risk is concentrated on multi-tenant vGPU, VDI and cloud-GPU hosts that run untrusted guests rather than single-tenant hosts with trusted workloads.
An out-of-bounds write in the kernel-mode layer of the NVIDIA vGPU Virtual GPU Manager for Windows and Linux allows a local attacker holding low privileges to corrupt kernel memory and potentially achieve code execution, privilege escalation, denial of service, information disclosure, and data tampering (CVSS 3.1 base 7.8). The flaw is local-only (AV:L) and requires an existing low-privileged foothold (PR:L) with no user interaction (UI:N); there is no public exploit identified at time of analysis and the package is not listed in CISA KEV. Although the numeric score is High, practical risk is assessed as MODERATE because exploitation demands local code execution on a host that specifically runs the vGPU manager - a component found in vGPU/VDI and cloud-GPU deployments rather than ordinary consumer driver installs.
Missing authorization in the NVIDIA vGPU GPU kernel driver lets a low-privileged user inside a guest VM reach privileged host GPU resources on Windows and Linux hosts, giving up to code execution, privilege escalation, data tampering, denial of service, and information disclosure on the hypervisor-side GPU stack. Exploitation requires local code execution within a guest (CVSS AV:L, PR:L, UI:N) in a vGPU deployment, so it is a realistic escalation primitive for tenants of shared-GPU, VDI, and cloud desktops rather than an internet-facing issue. No public exploit identified at time of analysis; risk is operator-context-dependent, but the high CIA impact and easy automation make prioritization relevant wherever untrusted tenants share vGPU capacity. Authentication requirements are confirmed as low-privileged/authenticated (CVSS vector PR:L).
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.
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.
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.
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.
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.
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.
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 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.
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.
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 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 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 and code execution in NVIDIA Virtual GPU Manager arises from a use-after-free on stack memory within the vGPU hypervisor component. Authenticated local attackers on the host or guest side of an affected vGPU deployment (vGPU branches 16.x through 20.x) can trigger memory corruption that may yield DoS, info disclosure, data tampering, or arbitrary code execution. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC rates 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 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.
Improper numeric conversion in NVIDIA vGPU Virtual GPU Manager for Linux can be triggered from the kernel-mode layer by a local attacker who already holds high privileges, potentially enabling code execution, denial of service, privilege escalation, information disclosure, or data tampering. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) shows the dominant constraint is PR:H: an unprivileged guest or local user cannot reach the vulnerable path, and only Linux vGPU Manager deployments are in scope. No public exploit or CISA KEV confirmation is identified at time of analysis; this is a genuine but not urgent issue requiring a privileged local actor.
An out-of-bounds read in the kernel-mode layer of NVIDIA's vGPU Virtual GPU Manager for Linux allows a local, already highly privileged user on the hypervisor host to drive the driver past the bounds of an allocated buffer, with the potential for kernel code execution, privilege escalation, information disclosure, denial of service, or data tampering. The issue is rated CVSS 3.1 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and is confined to Linux hosts running the Virtual GPU Manager in vGPU/VDI or cloud-GPU deployments; no public exploit has been identified at time of analysis. Because the attacker must already be authenticated with high privileges on the host and the attack surface is local-only, this is a moderate-priority, defense-in-depth issue rather than an urgent remote threat.
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.
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.
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 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.
Out-of-bounds write in NVIDIA Virtual GPU Manager exposes virtualized GPU deployments to denial of service, data tampering, and information disclosure. A local, low-privileged attacker operating within a virtualized environment can trigger the memory corruption flaw in the host-side vGPU manager component across multiple affected driver branches (vGPU 16.x through 20.x). No public exploit code exists at time of analysis, and EPSS probability is at the 2nd percentile, but the high availability impact (A:H in CVSS) and the prevalence of vGPU in enterprise virtualization infrastructure warrant prompt patching.
NVIDIA Display Driver for Linux exposes a denial-of-service condition in the Multi-Instance GPU (MIG) partition management subsystem, rooted in insecure default initialization of memory subsystem routing resources (CWE-1188). A local authenticated user - with low privileges on a Linux system running MIG-enabled Tesla, GeForce, RTX/Quadro/NVS, or Virtual GPU Manager driver branches - can trigger a hang or data corruption during partition reconfiguration, potentially disrupting all GPU workloads sharing the affected physical GPU. No public exploit code exists and this vulnerability is not in CISA KEV; EPSS sits at 0.01% (2nd percentile), indicating no observed mass exploitation at time of analysis.
Race condition exploitation in NVIDIA Display Driver's Linux kernel module allows a local authenticated user to cause denial of service by manipulating compiler or processor memory instruction ordering. Affected product lines span GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver across multiple driver branches up to the March 2026 release. No active exploitation has been confirmed - this is not listed in CISA KEV, EPSS is 0.01% (1st percentile), and SSVC assessment classifies exploitation status as none - placing this firmly in a patch-and-monitor category rather than emergency response.
Denial of service in NVIDIA Display Driver for Windows and Linux stems from improper lock management (CWE-667), where an attacker with local low-privilege access can leak held driver locks, potentially crashing or hanging the driver stack and denying GPU availability system-wide. Scope is changed (S:C), meaning the impact extends beyond the vulnerable component to the broader kernel or hypervisor layer. No public exploit identified at time of analysis and no CISA KEV listing; EPSS at 0.01% (1st percentile) and SSVC exploitation status of 'none' consistently signal low near-term exploitation likelihood.
NVIDIA vGPU driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin), which could allow an attacker to retrieve information that could lead to a Address Space Layout Randomization. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin) where it allows guests to control unauthorized resources, which may lead to integrity and confidentiality loss or. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin), where there is the potential to write to a shared memory location and manipulate the data after the data has been. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU driver contains a vulnerability in the guest kernel mode driver and Virtual GPU Manager (vGPU plugin), in which an input length is not validated, which may lead to information disclosure,. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and Virtual GPU Manager (vGPU plugin), in which an input length is not validated, which may lead to information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (vGPU plugin), in which an input length is not validated, which may lead to information disclosure, tampering of data, or. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and Virtual GPU manager (vGPU plugin), in which an input length is not validated, which may lead to information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (vGPU plugin), in which certain input data is not validated, which may lead to information disclosure, tampering of data, or. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which input data is not validated, which may lead to unexpected consumption of resources, which in turn may lead to denial of. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which input data is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which it obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer, which. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which an input offset is not validated, which may lead to a buffer overread, which in turn may cause tampering of data, information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which an input data length is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which a race condition may cause the vGPU plugin to continue using a previously validated resource that has since changed, which. Rated medium severity (CVSS 6.3). No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and vGPU plugin, in which an input index is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which an input index is not validated, which may lead to integer overflow, which in turn may cause tampering of data, information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and vGPU plugin, in which an input data size is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager NVIDIA vGPU manager contains a vulnerability in the vGPU plugin in which it allows guests to allocate some resources for which the guest is not authorized, which may lead. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which it can dereference a NULL pointer, which may lead to denial of service. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which allocated memory can be freed twice, which may lead to information disclosure or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin in which guest-supplied parameters remain writable by the guest after the plugin has validated them, which may lead to the guest. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which an input data size is not validated, which may lead to tampering or denial of service. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which an input data length is not validated, which may lead to tampering or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin in which it may have the use-after-free vulnerability while freeing some resources, which may lead to denial of service, code. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin and the host driver kernel module, in which the potential exists to write to a memory location that is outside the intended. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in the kernel mode layer (nvlddmkm.sys) scheduler, in which the software does not properly limit the number or frequency of. Rated medium severity (CVSS 4.4), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in the DirectX11 user mode driver (nvwgf2um/x.dll), in which a specially crafted shader can cause an out of bounds access,. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in multiple components in which a securely loaded system DLL will load its dependencies in an insecure fashion, which may. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
Out-of-bounds write in the NVIDIA Virtual GPU Manager (vGPU plugin) lets an unprivileged user inside an assigned guest VM corrupt host-side memory by sending a specially crafted RPC call across the virtualization channel, resulting in privilege escalation, data tampering, and denial of service on the host. Rated CVSS 7.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H), the bug is only reachable in vGPU/VDI/cloud-GPU deployments where the host runs the vGPU plugin and has at least one guest assigned; it is not a network-facing flaw and does not affect standard bare-metal Linux GPU driver installs, and no public exploit code has been identified at time of analysis. Real-world risk is therefore defined by the attack surface rather than by mass exploitability, since a successful attack requires an attacker to already hold an unprivileged local account inside a hosted guest VM.
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned, low-privileged attacker to break an internal resource-handling boundary and gain high-integrity impact - code execution, privilege escalation, data tampering, information disclosure, or denial of service on the host running the vGPU Manager. This affects virtualization/vGPU deployments on Linux (the manager component on the hypervisor host), not standard desktop GPU drivers, and the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confirms the attacker must already hold local low-privileged access to a context served by that manager, such as a guest VM or a local account on the host; there is no network or unauthenticated path. It is a genuine local privilege-escalation class issue rather than a remotely triggerable one, and no public exploit was identified at time of analysis.
An out-of-bounds write in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker with low privileges corrupt kernel memory, which the vendor rates as potentially leading to code execution, denial of service, privilege escalation, information disclosure, and data tampering (CVSS 3.1 base 7.8, HIGH). The attack is strictly local - vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - so it is not remotely exploitable and requires only an authenticated low-privileged context or a tenant/guest that can reach the host kernel module; the risk is highest in multi-tenant VDI and cloud-GPU deployments where local access is comparatively easy to obtain. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so there is no evidence of confirmed active exploitation.
Local privilege escalation, code execution, denial of service, and information disclosure affect Linux hosts running NVIDIA vGPU Virtual GPU Manager because of an out-of-bounds read in the kernel-mode layer that services vGPU requests. A low-privileged local account or existing code-execution context (CVSS PR:L) is required, and no user interaction is needed, but the flaw is not remotely reachable and only impacts hosts with the vGPU Manager component installed. No public exploit or proof-of-concept has been identified at time of analysis, and EPSS data was not provided; the independent assessment rates this as a moderate, locally-scoped risk.
Local privilege escalation in NVIDIA vGPU Virtual GPU Manager for Linux stems from an out-of-bounds read in firmware (CWE-125) that a low-privileged local attacker can trigger with no user interaction and low complexity. The CVSS 3.1 score is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting high confidentiality, integrity, and availability impact on vGPU/VDI/cloud-GPU hosts that use the affected Linux Virtual GPU Manager. No public exploit was identified at time of analysis, and exploitation requires an existing local foothold; it is not remotely exploitable despite the RCE tag.
Local attackers with low privileges on a Linux host running NVIDIA vGPU Virtual GPU Manager can trigger an out-of-bounds read in the kernel-mode layer, potentially leading to code execution, privilege escalation, denial of service, information disclosure, and data tampering. The flaw is not remotely reachable and affects only virtualization, VDI, or cloud-GPU hosts that run the vGPU Manager. No public exploit code or active exploitation has been identified at time of analysis.
Out-of-bounds read in NVIDIA vGPU Virtual GPU Manager for Linux allows a local authenticated attacker with low privileges to potentially achieve code execution, denial of service, or information disclosure. The vulnerability resides in the kernel-mode driver and affects both the vGPU Manager and guest driver components. No public exploit code has been identified, and the flaw is not known to be actively exploited. Integrity impact is assessed as low, but confidentiality and availability impacts are high, making this a significant risk in multi-tenant vGPU deployments.
An out-of-bounds read in the kernel-mode layer of the NVIDIA vGPU Virtual GPU Manager for Linux lets a local attacker who can already reach the vGPU kernel interface trigger memory reads past the bounds of an allocated buffer, potentially yielding information disclosure, data tampering, privilege escalation, denial of service, or kernel code execution. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning it is only reachable by an authenticated local principal - a low-privileged user or a guest context on the hypervisor - and not by an unauthenticated remote network attacker. Exposure is limited to hosts that actually deploy NVIDIA vGPU on Linux (VDI and cloud-GPU virtualization platforms), where the highest-impact scenario is a multi-tenant deployment in which the over-read crosses tenant isolation boundaries; no public exploit code or CISA KEV entry was identified at time of analysis, so this is a genuine but not emergency-grade issue warranting scheduled patching.
An out-of-bounds write in the NVIDIA Virtual GPU Manager (vGPU plugin) for Linux allows a user who already holds a low-privileged account inside a guest VM to corrupt host-side memory by sending a crafted RPC message whose performance-state list size parameters are invalid, potentially yielding code execution, privilege escalation, data tampering, denial of service, or information disclosure across the virtualization boundary. The defect is locally triggered (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) and requires no user interaction, but it is only reachable on hosts actually running the vGPU Manager for multi-tenant vGPU/VDI/cloud-GPU workloads - single-tenant systems without vGPU virtualization are not exposed through this guest-to-host path. No public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV); exploitability is constrained by the need for prior guest authentication and the presence of the vGPU component, making this a contained but genuine virtualization-trust-boundary flaw rather than a broad remote threat.
Out-of-bounds read (CWE-125) in the kernel-mode layer of NVIDIA's vGPU Virtual GPU Manager for Windows and Linux allows a low-privileged process inside a guest VM to force the host-side vGPU driver to read past the end of an allocated buffer (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), primarily exposing host memory contents and creating crash and denial-of-service risk, with code execution and privilege escalation described by the vendor only as possible rather than demonstrated. The issue is reachable only on hosts actively running vGPU configurations such as VDI or cloud GPU hosting where an attacker already holds a foothold inside a guest; bare-metal and non-vGPU installations are not affected, and no user interaction or network reach is required. No public exploit code or confirmed active exploitation has been identified at time of analysis, and no fixed driver version appears in the available intelligence, so defenders should treat patch confirmation through NVIDIA's advisory as the priority action.
An out-of-bounds write in NVIDIA vGPU Manager's GPU System Processor (GSP) plugin lets an authenticated user inside a guest VM hit host-side plugin code with a specially crafted RPC message, potentially yielding code execution, privilege escalation, data tampering, denial of service, or information disclosure in the virtualization host stack. The practical barrier is an existing foothold in an authorized vGPU guest rather than network reachability, and no public exploit code has been identified at time of analysis. Scoring 7.8 under CVSS 3.1 (AV:L/AC:L/PR:L/UI:N, with high confidentiality, integrity, and availability impact) it represents a Moderate, locally-scoped risk that matters most in multi-tenant vGPU deployments where guest-to-host isolation is a core control.
Improper access through a buffer shared between a guest VM and the host in NVIDIA Virtual GPU Manager's GPU System Processor (GSP) tracing component (CWE-367, time-of-check-to-time-of-use) can lead to code execution, privilege escalation, data tampering, denial of service and information disclosure on the affected host. Exploitation is local rather than network-facing: the attacker must already hold user-level code execution inside a vGPU-attached guest VM and must additionally win a timing-dependent race against the host-side tracing path (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H per independent assessment). No public exploit code and no confirmed active exploitation were identified at time of analysis, so practical risk is concentrated on multi-tenant vGPU, VDI and cloud-GPU hosts that run untrusted guests rather than single-tenant hosts with trusted workloads.
An out-of-bounds write in the kernel-mode layer of the NVIDIA vGPU Virtual GPU Manager for Windows and Linux allows a local attacker holding low privileges to corrupt kernel memory and potentially achieve code execution, privilege escalation, denial of service, information disclosure, and data tampering (CVSS 3.1 base 7.8). The flaw is local-only (AV:L) and requires an existing low-privileged foothold (PR:L) with no user interaction (UI:N); there is no public exploit identified at time of analysis and the package is not listed in CISA KEV. Although the numeric score is High, practical risk is assessed as MODERATE because exploitation demands local code execution on a host that specifically runs the vGPU manager - a component found in vGPU/VDI and cloud-GPU deployments rather than ordinary consumer driver installs.
Missing authorization in the NVIDIA vGPU GPU kernel driver lets a low-privileged user inside a guest VM reach privileged host GPU resources on Windows and Linux hosts, giving up to code execution, privilege escalation, data tampering, denial of service, and information disclosure on the hypervisor-side GPU stack. Exploitation requires local code execution within a guest (CVSS AV:L, PR:L, UI:N) in a vGPU deployment, so it is a realistic escalation primitive for tenants of shared-GPU, VDI, and cloud desktops rather than an internet-facing issue. No public exploit identified at time of analysis; risk is operator-context-dependent, but the high CIA impact and easy automation make prioritization relevant wherever untrusted tenants share vGPU capacity. Authentication requirements are confirmed as low-privileged/authenticated (CVSS vector PR:L).
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.
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.
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.
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.
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.
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.
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 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.
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.
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 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 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 and code execution in NVIDIA Virtual GPU Manager arises from a use-after-free on stack memory within the vGPU hypervisor component. Authenticated local attackers on the host or guest side of an affected vGPU deployment (vGPU branches 16.x through 20.x) can trigger memory corruption that may yield DoS, info disclosure, data tampering, or arbitrary code execution. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC rates 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 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.
Improper numeric conversion in NVIDIA vGPU Virtual GPU Manager for Linux can be triggered from the kernel-mode layer by a local attacker who already holds high privileges, potentially enabling code execution, denial of service, privilege escalation, information disclosure, or data tampering. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) shows the dominant constraint is PR:H: an unprivileged guest or local user cannot reach the vulnerable path, and only Linux vGPU Manager deployments are in scope. No public exploit or CISA KEV confirmation is identified at time of analysis; this is a genuine but not urgent issue requiring a privileged local actor.
An out-of-bounds read in the kernel-mode layer of NVIDIA's vGPU Virtual GPU Manager for Linux allows a local, already highly privileged user on the hypervisor host to drive the driver past the bounds of an allocated buffer, with the potential for kernel code execution, privilege escalation, information disclosure, denial of service, or data tampering. The issue is rated CVSS 3.1 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and is confined to Linux hosts running the Virtual GPU Manager in vGPU/VDI or cloud-GPU deployments; no public exploit has been identified at time of analysis. Because the attacker must already be authenticated with high privileges on the host and the attack surface is local-only, this is a moderate-priority, defense-in-depth issue rather than an urgent remote threat.
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.
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.
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 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.
Out-of-bounds write in NVIDIA Virtual GPU Manager exposes virtualized GPU deployments to denial of service, data tampering, and information disclosure. A local, low-privileged attacker operating within a virtualized environment can trigger the memory corruption flaw in the host-side vGPU manager component across multiple affected driver branches (vGPU 16.x through 20.x). No public exploit code exists at time of analysis, and EPSS probability is at the 2nd percentile, but the high availability impact (A:H in CVSS) and the prevalence of vGPU in enterprise virtualization infrastructure warrant prompt patching.
NVIDIA Display Driver for Linux exposes a denial-of-service condition in the Multi-Instance GPU (MIG) partition management subsystem, rooted in insecure default initialization of memory subsystem routing resources (CWE-1188). A local authenticated user - with low privileges on a Linux system running MIG-enabled Tesla, GeForce, RTX/Quadro/NVS, or Virtual GPU Manager driver branches - can trigger a hang or data corruption during partition reconfiguration, potentially disrupting all GPU workloads sharing the affected physical GPU. No public exploit code exists and this vulnerability is not in CISA KEV; EPSS sits at 0.01% (2nd percentile), indicating no observed mass exploitation at time of analysis.
Race condition exploitation in NVIDIA Display Driver's Linux kernel module allows a local authenticated user to cause denial of service by manipulating compiler or processor memory instruction ordering. Affected product lines span GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver across multiple driver branches up to the March 2026 release. No active exploitation has been confirmed - this is not listed in CISA KEV, EPSS is 0.01% (1st percentile), and SSVC assessment classifies exploitation status as none - placing this firmly in a patch-and-monitor category rather than emergency response.
Denial of service in NVIDIA Display Driver for Windows and Linux stems from improper lock management (CWE-667), where an attacker with local low-privilege access can leak held driver locks, potentially crashing or hanging the driver stack and denying GPU availability system-wide. Scope is changed (S:C), meaning the impact extends beyond the vulnerable component to the broader kernel or hypervisor layer. No public exploit identified at time of analysis and no CISA KEV listing; EPSS at 0.01% (1st percentile) and SSVC exploitation status of 'none' consistently signal low near-term exploitation likelihood.
NVIDIA vGPU driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin), which could allow an attacker to retrieve information that could lead to a Address Space Layout Randomization. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin) where it allows guests to control unauthorized resources, which may lead to integrity and confidentiality loss or. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU driver contains a vulnerability in the Virtual GPU Manager (vGPU plugin), where there is the potential to write to a shared memory location and manipulate the data after the data has been. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU driver contains a vulnerability in the guest kernel mode driver and Virtual GPU Manager (vGPU plugin), in which an input length is not validated, which may lead to information disclosure,. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and Virtual GPU Manager (vGPU plugin), in which an input length is not validated, which may lead to information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (vGPU plugin), in which an input length is not validated, which may lead to information disclosure, tampering of data, or. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and Virtual GPU manager (vGPU plugin), in which an input length is not validated, which may lead to information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (vGPU plugin), in which certain input data is not validated, which may lead to information disclosure, tampering of data, or. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which input data is not validated, which may lead to unexpected consumption of resources, which in turn may lead to denial of. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which input data is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which it obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer, which. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which an input offset is not validated, which may lead to a buffer overread, which in turn may cause tampering of data, information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which an input data length is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which a race condition may cause the vGPU plugin to continue using a previously validated resource that has since changed, which. Rated medium severity (CVSS 6.3). No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and vGPU plugin, in which an input index is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU manager contains a vulnerability in the vGPU plugin, in which an input index is not validated, which may lead to integer overflow, which in turn may cause tampering of data, information. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA vGPU software contains a vulnerability in the guest kernel mode driver and vGPU plugin, in which an input data size is not validated, which may lead to tampering of data or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager NVIDIA vGPU manager contains a vulnerability in the vGPU plugin in which it allows guests to allocate some resources for which the guest is not authorized, which may lead. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which it can dereference a NULL pointer, which may lead to denial of service. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which allocated memory can be freed twice, which may lead to information disclosure or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin in which guest-supplied parameters remain writable by the guest after the plugin has validated them, which may lead to the guest. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which an input data size is not validated, which may lead to tampering or denial of service. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin, in which an input data length is not validated, which may lead to tampering or denial of service. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin in which it may have the use-after-free vulnerability while freeing some resources, which may lead to denial of service, code. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Virtual GPU Manager contains a vulnerability in the vGPU plugin and the host driver kernel module, in which the potential exists to write to a memory location that is outside the intended. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in the kernel mode layer (nvlddmkm.sys) scheduler, in which the software does not properly limit the number or frequency of. Rated medium severity (CVSS 4.4), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in the DirectX11 user mode driver (nvwgf2um/x.dll), in which a specially crafted shader can cause an out of bounds access,. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
NVIDIA Windows GPU Display Driver, all versions, contains a vulnerability in multiple components in which a securely loaded system DLL will load its dependencies in an insecure fashion, which may. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.