Nvidia
Monthly
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Unauthenticated remote attackers can tamper with token state and disrupt service availability in NVIDIA AIStore for Linux by sending crafted token-revocation lists to a token-revocation endpoint that performs no authentication check (CVSS 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H). Because the vector shows PR:N and UI:N, no credentials, privileges, or user interaction are needed - any network-reachable deployment of the affected endpoint is directly exploitable, with the only practical limiting factor being firewall or segmentation controls around the AIStore management/control interface. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but the missing authentication control (CWE-306) is the defect itself, so the issue should be treated as a genuine high-priority exposure rather than an inflated score.
Missing authorization in the NVIDIA AIStore ETL management API lets remote, unauthenticated attackers read ETL job information and issue start or stop operations against existing extract-transform-load pipelines by sending crafted GET or POST requests to an AIStore proxy (CVE-2026-65172, CVSS 8.6, CWE-862). Per the assessed vector (AV:N/AC:L/PR:N/UI:N, C:H/I:L/A:L), no credentials or user interaction are required; the practical constraint is network reachability to a proxy that exposes the ETL management API in Linux or Kubernetes deployments. No public exploit code and no confirmed active exploitation were identified at time of analysis, so the immediate risk is driven by exposure of the proxy API rather than by observed attack activity.
Unauthenticated remote attackers can abuse NVIDIA AIStore's experimental HT backend to perform server-side request forgery by supplying a crafted 'original URL' value, causing the AIStore server to issue requests to attacker-chosen destinations and disclose information reachable from the server's network position. The flaw carries a CVSS 3.1 score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N), reflecting no authentication or user interaction requirement and a scope change, with impact confined to confidentiality - integrity and availability are unaffected. There is no public exploit identified at time of analysis, and the practical risk is gated almost entirely on whether the experimental HT backend has been enabled on a network-exposed deployment, since that component is not part of the default AIStore configuration and is only reachable in non-standard setups.
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
Unauthenticated remote attackers can achieve code execution and privilege escalation against NVIDIA AIStore for Linux by injecting arbitrary Kubernetes host-namespace and container security settings into the legacy ETL Kubernetes PodSpec initialization API, rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) because the impact escapes the AIStore workload and extends to the underlying Kubernetes node and cluster. The vector confirms the attack is network-reachable with no privileges or user interaction required, though practical exploitation depends on the legacy ETL/transformation feature being enabled and the ETL API being exposed, and on Kubernetes RBAC and PodSecurity admission being permissive enough for AIStore to actually schedule host-namespaced or privileged pods. At time of analysis there is no confirmed active exploitation (CISA KEV) and no public exploit code identified, but the vendor-reported severity, the scope-changed impact, and CWE-250 (execution with unnecessary privileges) place this in top-priority territory for any cluster running an exposed AIStore ETL endpoint.
Unauthenticated path traversal in the NVIDIA AIStore Promote API on Linux lets a remote attacker read arbitrary files that the AIStore process can access by supplying a crafted absolute source path, resulting in high-confidentiality information disclosure (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Any network-reachable deployment where the Promote endpoint is enabled and functional is at risk, since the vector requires no authentication (PR:N) and no user interaction (UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical blast radius is bounded by the OS privileges of the AIStore process account and by whether the Promote API is exposed beyond trusted internal networks, making this a genuine but moderate-priority issue rather than a critical emergency.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Hash collisions in the inference request cache of NVIDIA Megatron-LM let an attacker who can already submit inference requests tamper with cached data and obtain partial information about other users' cached requests and responses, yielding a CVSS 7.1 impact (AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N). Because the cache key relies on a weak hash (CWE-328), success depends on the attacker engineering colliding inputs against an enabled, shared inference cache, which is why the vector rates complexity as high rather than trivial. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; this is a moderate-severity issue rather than a top-tier emergency, and the NVIDIA product-security advisory is the authoritative source for affected builds and fixed versions.
Unauthenticated path traversal in the target-side object rename handler of NVIDIA AIStore on Linux allows a remote attacker who can reach a target (storage) node directly to write files outside the intended storage directory by supplying a crafted rename destination, resulting in arbitrary file creation or overwrite. NVIDIA rates the issue CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-22), with downstream consequences that could include code execution, privilege escalation, information disclosure, data tampering, and denial of service depending on what the overwritten path controls. Exploitation is constrained rather than trivial: the attacker needs network reachability to a target node - not merely the front-end proxy - and must build a traversal payload the rename handler accepts, so exposure is greatest in flat cluster networks or environments where target ports are directly reachable; no public exploit code and no CISA KEV entry were identified at time of analysis.
Server-side request forgery in NVIDIA AIStore for Linux's distributed sort (dsort) component allows remote unauthenticated attackers to make an AIStore node issue outbound HTTP requests to an arbitrary URL by supplying a crafted external key map URL, resulting in disclosure of information from internal or otherwise unreachable services. The CVSS 3.1 base score is 8.6 (High) via AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N, meaning the attack is network reachable, low complexity, requires no privileges and no user interaction, with the impact limited to confidentiality (integrity and availability are unaffected). At time of analysis no public exploit code has been identified, there is no CISA KEV listing for this CVE, and no EPSS score was supplied in the available data.
Stack-based buffer overflow in NVIDIA DALI lets a locally authenticated, low-privileged user who can get a crafted input file processed through a DALI pipeline corrupt memory and potentially achieve code execution, information disclosure, data tampering, or denial of service. Per the assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3 High), exploitation is not remotely reachable: it requires an existing local foothold with at least low privileges plus some form of user interaction, which in practice means a victim or automated process must load attacker-controlled data. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; the practical risk concentrates on multi-tenant or pipeline-automation GPU hosts where untrusted files are routinely fed into DALI. Exact affected versions are unconfirmed because the CPE is a wildcard, so defenders must verify their deployed DALI build against the NVIDIA advisory.
An uncontrolled out-of-bounds read in NVIDIA DALI (Data Loading Library) can be triggered when a low-privileged local user processes specially crafted input through a DALI data-loading or augmentation pipeline (CVSS 3.1 base 7.3, AV:L/AC:L/PR:L/UI:R), resulting in memory disclosure, data tampering, and denial of service. Impact is bounded by the local attack vector and the requirement for both low privileges and user interaction - an unauthenticated remote attacker cannot trigger it directly, and an idle default installation is not exploitable. Exposure is greatest in workflows where DALI ingests untrusted or externally sourced datasets and media; the CPE record (cpe:2.3:a:nvidia:dali:*:*:*:*:*:*:*:*) indicates the issue is not version-scoped in the supplied data, and no public exploit code or CISA KEV entry has been identified at time of analysis.
An uncontrolled out-of-bounds write in NVIDIA DALI (the Data Loading Library used for GPU-accelerated data preprocessing) allows a locally positioned attacker who already holds low-level privileges to corrupt process memory when a DALI pipeline loads or decodes attacker-influenced input such as a crafted image, media file, or dataset record. A successful exploit can produce denial of service, information disclosure, and data tampering, consistent with the vendor rating of 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), which requires local access, low privileges, and user interaction (a victim or process must ingest the malicious data). There is no CISA KEV listing and no public exploit identified at time of analysis, so practical risk is concentrated in multi-tenant training clusters, pipelines consuming externally sourced datasets, and services that accept user-submitted media for GPU preprocessing rather than in default in-house-only deployments.
An uncontrolled out-of-bounds read in NVIDIA DALI is triggered while the library parses attacker-supplied data inside a data-loading pipeline, allowing crafted input to expose process memory contents and crash the workload, which results in information disclosure and denial of service. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:H) the attack is local, requires the attacker to already hold low-level privileges on the host, and critically depends on user interaction - a user or training job must actually run DALI over the malicious sample, so environments that ingest only trusted, internally generated data are effectively not exposed. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); this is a moderate, not top-tier, priority.
Eval injection in NVIDIA Isaac Lab allows a local attacker who can supply crafted input - such as a malicious experiment configuration, task/environment definition, or command-line parameter - to achieve arbitrary code execution, information disclosure, data tampering, and denial of service once a user opens, loads, or runs the content. The flaw is rated CVSS 7.8 (HIGH) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: no privileges are required (PR:N) but the victim must interact with the malicious input (UI:R), the attack path is local (AV:L), and impact is scoped to the invoking user (S:U), so no privilege escalation is implied. The CPE entry is a wildcard with no version boundary and no fixed version is published in the available data, so all Isaac Lab releases should be treated as potentially affected; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Deserialization of untrusted data in NVIDIA Model-Optimizer (CVSS 3.1 base score 7.8) allows an attacker who supplies a crafted model artifact to achieve code execution, data tampering, denial of service, and information disclosure on the machine that loads it. The assessed vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) shows the severity comes from full loss of confidentiality and integrity once the payload runs, but the attacker must first get the victim to open or deserialize the malicious artifact in a local processing environment, so there is no remote, zero-interaction path. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so this is a credible but priority-setting issue for ML/AI pipelines that ingest third-party models rather than an emergency remote-exploitation case.
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.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Out-of-bounds write in the NVIDIA GPU Display Driver for Windows kernel module can let a local, authenticated low-privileged user execute code, escalate privileges, cause denial of service, disclose information, or tamper with data on affected GeForce, RTX/Quadro/NVS, and Tesla systems. Exploitation requires local access to the GPU-equipped Windows host plus a low-privileged account able to reach the kernel module, and the high attack complexity means it is not reliably one-shot; multi-user, VDI, and cloud/virtual-GPU environments are the main risk. No public exploit identified at time of analysis, and CVSS is 7.0 with high confidentiality, integrity, and availability impact.
Denial of service and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.
An out-of-bounds read in the NVIDIA Display Driver for Windows kernel module allows local attackers to cause denial of service and disclose sensitive kernel memory. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver lines on Windows; exploitation requires local access with no elevated privileges or user interaction. No public exploit code has been identified, and the vulnerability is not remotely exploitable.
Authenticated low-privileged local users can bypass cryptographic signature verification in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux when the system is under memory pressure, leading to data tampering and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver branches on Linux; no public exploit code has been identified at time of analysis. Our assessment rates this as a genuine but bounded-priority local issue because the attacker must reliably induce a low-memory kernel state at the moment of verification, making exploitation opportunistic rather than dependable.
Information disclosure and data tampering can be achieved by a local low-privileged attacker exploiting a missing authorization check in the NVIDIA GPU Display Driver for Windows kernel module. Affected products include the GeForce, RTX/Quadro/NVS, and Tesla driver branches on Windows; exploitation requires local authenticated access (PR:L) and no user interaction (UI:N). No public exploit code or active exploitation has been identified at time of analysis; the CVSS score is 7.3 with scope change (S:C) that amplifies risk in multi-user or cloud-GPU environments.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux can be achieved by an unprivileged local user through the open-source kernel module's DMA-BUF import path, where importing a read-only buffer from another device's DMA-BUF exporter improperly preserves memory access permissions. Successful exploitation can result in code execution, privilege escalation, denial of service, information disclosure, and data tampering, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, and no CISA KEV entry is present in the provided data.
Local privilege escalation and kernel-level code execution in the NVIDIA GPU Display Driver for Windows and Linux, where the kernel-mode layer follows an error-handling path that operates on an improperly initialized resource (CWE-908). The flaw is reachable by an authenticated, low-privileged local user (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) on any host where the affected driver is installed and loaded, granting full confidentiality, integrity, and availability impact within the kernel-mode driver's scope. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); risk is concentrated on shared multi-tenant GPU hosts such as VDI, cloud GPU instances, and vGPU guests where untrusted local users coexist with the driver, and success may be probabilistic because the attacker must reliably trigger the failing error path.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in the NVIDIA GPU Display Driver's open-source kernel module lets an unprivileged local user trigger a use-after-free in the Resource Server map cleanup path via a missing self-reference guard, yielding code execution, privilege escalation, denial of service, information disclosure and data tampering (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, CWE-416). Affected are Windows and Linux hosts running the open-source kernel module variant of the driver, spanning GeForce, RTX/Quadro/NVS and Tesla product lines per the published CPEs; exploitation requires only a normal local account and no user interaction, but is strictly local with no network vector. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical risk is highest in shared or multi-tenant GPU environments (vGPU, VDI, cloud GPU) where gaining kernel-level control of the GPU driver crosses a meaningful tenant boundary.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a use-after-free (CWE-416) reachable by a low-privileged local user who can issue a crafted sequence of driver commands. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high, with the greatest risk in shared or virtualized GPU deployments where guest-driver or virtual GPU manager isolation may be broken. No public exploit code or confirmed active exploitation is identified in the available data, and EPSS is not provided; exploitation requires local access and construction of the specific command sequence.
Local privilege escalation in NVIDIA Display Driver for Windows allows an authenticated low-privileged user to trigger a stack-based out-of-bounds write in the kernel mode layer, potentially leading to code execution, privilege escalation, and denial of service. Affected systems include Windows hosts with GeForce, RTX/Quadro/NVS, or Tesla drivers, as well as the Guest Driver in virtualized deployments. No public exploit code or active exploitation has been identified at time of analysis, and the flaw requires local access, making it most relevant to shared multi-tenant environments.
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authenticated unprivileged user to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPUs, as well as Guest Driver and vGPU Manager deployments. With a CVSS score of 7.8, the vulnerability requires local access and low privileges (CVSS vector AV:L/AC:L/PR:L/UI:N), making it primarily a risk in multi-user or shared-GPU environments; no public exploit has been identified at time of analysis, and patched driver branches are available in NVIDIA security bulletin 5861.
Local privilege escalation in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows an unprivileged local user to bypass read-only memory protection and gain write access to memory the driver marked read-only, which can result in kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering. Exploitation requires the attacker to already hold low-privileged local access on an affected Linux host (CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N, score 7.8) with no user interaction and no network vector; the risk is greatest on shared, multi-tenant vGPU, VDI, and cloud-GPU hosts where crossing the user-to-kernel boundary breaks tenant isolation. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but NVIDIA has published a fix through security bulletin 5861. This is a genuine local privilege-escalation risk rather than an emergency, and it should be prioritized on multi-tenant GPU infrastructure.
Local privilege escalation in NVIDIA Display Driver for Windows and Linux allows an unprivileged local attacker to trigger a use-after-free condition by issuing a crafted sequence of driver commands, potentially achieving code execution, privilege escalation, denial of service, or information disclosure. The vulnerability affects systems with GeForce, RTX/Quadro/NVS, or Tesla GPUs running vulnerable driver versions. No public exploit identified at time of analysis.
Local privilege escalation and memory corruption in NVIDIA GPU Display Driver on Windows and Linux, affecting GeForce, RTX/Quadro/NVS, and Tesla lines. An unprivileged local user can trigger a use-after-free (CWE-416) by issuing a specific sequence of driver commands, leading to potential code execution, privilege escalation, denial of service, or information disclosure. Requires local access and low privileges (AV:L/PR:L) with no user interaction (UI:N); no public exploit identified at time of analysis. Risk is highest in multi-user or shared-GPU environments such as VDI, terminal servers, and cloud/virtualized GPU hosts.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, unprivileged user to trigger a use-after-free condition by issuing a specific sequence of driver commands, potentially leading to code execution, privilege escalation, denial of service, and information disclosure. The vulnerability affects GeForce, RTX/Quadro/NVS, and Tesla GPU drivers, including guest-VM vGPU deployments, and requires local access with low privileges. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Use-after-free in the NVIDIA GPU Display Driver for Linux allows a local, unprivileged user to corrupt driver memory by racing or abusing object lifetime handling, with a successful exploit potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The flaw scores 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is confined to local attackers who already hold an account on the GPU host, with no network vector and no user interaction required. This is a genuine but not emergency-grade issue: no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so realistic exposure is concentrated on shared or multi-tenant GPU systems - VDI desktops, cloud GPU instances, and HPC nodes - where untrusted users share a single driver instance.
An integer underflow (CWE-191) in the kernel-mode component of the NVIDIA GPU Display Driver for Windows lets a local, authenticated low-privileged user corrupt kernel memory in a way that can lead to code execution, privilege escalation, denial of service, information disclosure, or data tampering (CVSS 3.1: 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The issue affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches and is not network-reachable, so an attacker must already be able to run code as a normal user on the host. There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is concentrated on multi-user, VDI and cloud-GPU hosts where an unprivileged tenant shares the same machine as the vulnerable driver, while single-user desktops where the attacker must already hold a foothold face lower marginal risk.
Type confusion in the kernel-mode component of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution to corrupt kernel memory and potentially escalate to SYSTEM, crash the machine (BSOD/DoS), disclose kernel memory, or tamper with data. The issue is rated CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning the attacker must be local and authenticated with low privileges and no user interaction is required, and it affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is an access-gated local privilege-escalation risk rather than a remotely reachable mass-exploitation threat.
Local privilege escalation in NVIDIA Display Driver on Windows allows an authenticated low-privileged user to trigger a use-after-free in the kernel-mode driver, potentially enabling code execution with SYSTEM privileges, denial of service, information disclosure, or data tampering. The vulnerability requires local access and high attack complexity (AC:H) due to race conditions or kernel-pool reclamation, making reliable exploitation non-trivial, and it is not known to be actively exploited. The highest risk is in shared multi-user, VDI, or cloud-GPU environments where crossing a trust boundary from low-privileged user to kernel is significant.
Incorrect buffer size calculation in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution on the host to escalate to kernel-level privileges, with downstream risk of code execution, denial of service, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla data-center, and vGPU/Virtual GPU Manager drivers, and rates CVSS 3.1 base 7.8 (AV:L/AC:L/PR:L/UI:N) - it is strictly local, not remotely triggerable, so exposure is limited to shared workstations, multi-tenant vGPU/VDI environments, and cloud-GPU nodes where an untrusted party can already run code. No public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows allows an authenticated attacker with low-privileged code execution to exploit an integer overflow (CWE-190) in the kernel module, potentially achieving code execution, denial of service, information disclosure, and data tampering. The flaw requires local access (AV:L) and low privileges (PR:L) with no user interaction, affecting systems with GeForce, RTX/Quadro/NVS, or Tesla drivers. No public exploit code or active exploitation has been identified at the time of analysis; the CVSS 3.1 base score is 7.8 (HIGH).
Local code execution and denial of service on Windows systems with affected NVIDIA GPU Display Drivers stem from an integer overflow in the display driver's DIAG escape handler that results in an out-of-bounds write (CWE-787). An unprivileged local user (CVSS PR:L) can trigger the flaw via a device I/O call to the handler; no user interaction is required, and exploitation is confined to the local machine, meaning an attacker must already have a foothold. No public exploit identified at time of analysis (and no CISA KEV entry), but the shared-system impact-multi-user workstations, VDI, and cloud GPU instances-raises the risk profile.
An out-of-bounds write in NVIDIA NVAPI for Windows allows a locally authenticated attacker holding standard user privileges to corrupt memory by invoking NVAPI entry points, potentially leading to code execution, elevation of privileges, information disclosure, denial of service, or data tampering. The flaw affects hosts running the NVIDIA GPU driver package on Windows - including GeForce, RTX/Quadro/NVS, and Tesla driver-equipped systems - with a CVSS 3.1 base score of 7.8 (HIGH) under vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. No public exploit code and no confirmed active exploitation (CISA KEV) have been identified at time of analysis, but the local-only, low-privilege prerequisite makes shared and multi-tenant GPU/VDI hosts the most exposed environment.
Type confusion in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a local low-privileged user (CVSS vector AV:L/AC:L/PR:L/UI:N) who can reach the driver's device-node/ioctl interface to trigger memory corruption with high impact across confidentiality, integrity, and availability, potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The CVSS 3.1 base score of 7.8 reflects a local attack vector paired with uniformly high impacts rather than any remote reachability, and despite the 'RCE' tag in the source metadata the vulnerability is not remotely exploitable. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and no EPSS or CISA KEV signal was provided.
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
Local privilege escalation in NVIDIA GPU Display Driver for Windows (CUDA driver component) allows an authenticated attacker with low privileges to execute arbitrary code by planting a malicious library in an uncontrolled search path. Affected products include GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest driver branches. No public exploit identified at time of analysis; exploitation requires local access and write permissions to a directory resolved by the driver's search path, making it most relevant on shared multi-user or VDI/cloud-GPU hosts.
A type-confusion flaw in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux lets a local, low-privileged user who can open the driver's device nodes and issue ioctls trigger memory corruption by winning a handle-recycle race, yielding kernel-level code execution, privilege escalation, denial of service, information disclosure and data tampering. Affected platforms are the Linux driver branches covering GeForce, RTX/Quadro/NVS, Tesla/data-center GPUs and the vGPU guest driver and Virtual GPU Manager (CVSS 3.1 base 7.8; our independent assessment rates it AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, i.e. 7.0, because the race window makes exploitation timing-sensitive rather than deterministic). This is a local privilege-escalation-class issue with no remote vector: no public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), though it is most consequential on multi-user, VDI and cloud/virtualized GPU hosts where untrusted tenants share a single driver instance.
A NULL pointer dereference in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a locally present, low-privileged authenticated user to crash the driver - and potentially the kernel - by supplying a crafted request to the kernel-mode driver layer (for example via device ioctls). Affected platforms span the GeForce, RTX/Quadro/NVS, and Tesla driver lines on Linux, and the 'Guest Driver' / 'Virtual GPU Manager' tags indicate the vGPU path is also in scope, so a guest session inside a virtualized vGPU deployment is a valid attack position. The vendor claims the flaw 'might' lead to code execution, privilege escalation, information disclosure, and data tampering, but the reliably achievable outcome is a denial-of-service crash; there is no CISA KEV listing, no EPSS score provided, and no public exploit identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to trigger an out-of-bounds write in kernel memory via a crafted ioctl call with an unvalidated buffer size, enabling code execution, privilege escalation, information disclosure, and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla drivers, as well as Guest Driver and Virtual GPU Manager components, with highest risk in multi-tenant GPU environments such as VDI and cloud/HPC deployments. No public exploit identified at time of analysis; CVSS 3.1 score is 7.8 (local, low privileges, no user interaction).
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated unprivileged user to trigger a use-after-free in the kernel mode layer, potentially achieving code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw is reachable only by a locally authenticated low-privileged account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) that can issue ioctls to the GPU kernel-mode device interface; there is no remote attack path and no user interaction is required once a foothold exists. The 'Guest Driver' classification makes the issue most consequential in virtualized/vGPU and multi-tenant datacenter environments, where a low-privileged guest can reach the shared GPU driver. No public exploit identified at time of analysis, and the vendor advisory is the authoritative source for fixed driver versions.
Local privilege escalation in NVIDIA's GPU Display Driver (GeForce, RTX/Quadro/NVS, and Tesla, on both Windows and Linux) allows an authenticated low-privileged local user to reach GPU memory belonging to another process, enabling code execution, escalation of privileges, data tampering, denial of service, and information disclosure. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) there is no remote or network path; the flaw is most consequential on shared, multi-user, VDI, or multi-tenant GPU hosts where cross-process GPU memory isolation is the boundary between users and tenants. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the provided vendor reference points to NVIDIA's product security advisory (2026/5861) rather than a fixed driver version named in this data set.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel mode layer allows an authenticated, unprivileged user to trigger a double-free of imported memory state, potentially leading to code execution, denial of service, information disclosure, and data tampering. The flaw requires local access and a low-privilege account; no public exploit code or active exploitation has been identified at time of analysis. The CVSS 3.1 score is 7.8 (HIGH).
Local privilege escalation, code execution, denial of service, and information disclosure in NVIDIA GPU Display Driver on Windows and Linux stem from an integer overflow (CWE-190) in the kernel-mode layer that an unprivileged user can trigger to cause an out-of-bounds write. Exploitation requires local access with an existing low-privilege account (authenticated, PR:L) on a host with an affected GeForce, RTX/Quadro/NVS, or Tesla driver; the CVSS v3.1 base score is 7.8 (High) with a local attack vector (AV:L/AC:L/PR:L/UI:N). No public exploit code or CISA KEV entry was identified at the time of analysis, but the flaw is genuine and actionable for local privilege escalation if the vulnerable driver interface is reachable.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows an unprivileged local user to corrupt kernel memory, which can lead to code execution in the kernel, privilege escalation, denial of service, information disclosure, or data tampering. Systems running GeForce, RTX/Quadro/NVS, or Tesla driver packages on either operating system are affected; per the CVSS vector (AV:L, PR:L, UI:N) the flaw is reachable only by a user who already has local code execution on the host, making it a local privilege-escalation primitive rather than a remote entry point. No public exploit has been identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux stems from a missing authorization check in the kernel mode layer, allowing an unprivileged local user to modify privileged configuration and potentially achieve code execution, escalation of privileges, denial of service, information disclosure, and data tampering. Exploitation requires a pre-existing local low-privileged foothold (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), such as an unprivileged account on a host or inside a guest VM using the NVIDIA guest driver or Virtual GPU Manager, so this is an escalation primitive rather than a remote initial-access vector. No public exploit code is identified and no CISA KEV active exploitation is confirmed at time of analysis, but the high confidentiality, integrity, and availability impacts and broad affected driver families make patching a priority.
Use-after-free in the NVIDIA GPU Display Driver kernel mode layer (Windows and Linux) lets a local user who already holds low-privileged code execution on the host trigger a memory-corruption condition inside the kernel driver, with the potential for code execution, privilege escalation, information disclosure, data tampering, and denial of service. Affected platforms span consumer and professional GPU lines (GeForce, RTX/Quadro/NVS, Tesla) as well as the vGPU components, where a malicious or compromised guest can exercise the vulnerable path through the Guest Driver and Virtual GPU Manager. The attack is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, score 7.8), requires no user interaction and no non-default configuration beyond having the driver installed, and there is no public exploit identified at time of analysis - no KEV entry and no proof-of-concept code is referenced in the available data.
Local privilege escalation in NVIDIA GPU Display Drivers for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU) allows an unprivileged local user to execute code in kernel mode by supplying an untrusted pointer that the driver dereferences without validation. Affected hosts include multi-user and virtualized Windows systems with default driver installations, where exploitation can lead to escalation to SYSTEM, denial of service, information disclosure, and data tampering. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; the CVSS 3.1 base score is 7.8 (High).
A locally-triggered out-of-bounds write in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-level privileges on a Windows or Linux host corrupt kernel memory, with the potential for code execution in kernel context, escalation of privileges, denial of service, information disclosure and data tampering. The affected driver ships by default across the GeForce, RTX/Quadro/NVS, Tesla and Virtual GPU Manager product lines, so any host with a current NVIDIA driver installed is in scope, but exploitation is not remote: an attacker must first obtain code execution on the target (an authenticated local user, a compromised low-privileged process, or sandboxed code with driver access) and then develop a reliable kernel corruption exploit. CVE-2026-47548 carries a vendor/NVD CVSS 3.1 vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8, High); no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Local attackers with low-privileged code execution can trigger an out-of-bounds read (CWE-125) in the kernel-mode layer of the NVIDIA GPU Display Driver on Windows and Linux, which may lead to escalation of privileges, code execution, denial of service, information disclosure, and data tampering. This locally exploitable flaw (CVSS 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) affects GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager products, and no public exploit has been identified at the time of analysis. A vendor advisory with remediation guidance is available from NVIDIA via its product security page.
Integer underflow in the kernel-mode layer of NVIDIA GPU Display Driver for Windows and Linux allows a local attacker with low privileges to potentially achieve code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Manager products, and exploitation requires local access (CVSS AV:L) with no user interaction (UI:N) but low privileges (PR:L). No public exploit code has been identified at time of analysis, and there is no indication of active exploitation.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged authenticated user to corrupt kernel memory, with the potential to escalate privileges to kernel-level code execution, crash the system (denial of service), disclose information, or tamper with data. The flaw rates CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires pre-existing code execution as a standard user on a host with the driver loaded, but no user interaction and no non-default configuration; the vulnerable kernel-mode layer ships and loads by default once the driver is installed. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, but the affected GeForce, RTX/Quadro/NVS, and Tesla product families are extremely widely deployed, making this a genuine high-priority patch-management item rather than an emergency.
Local attackers with low privileges can exploit an uninitialized pointer access flaw (CWE-824) in the firmware of NVIDIA Display Driver for Windows and Linux to achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering. The vulnerability requires local access (AV:L) and authenticated low-privilege credentials (PR:L); no public exploit identified at time of analysis. Affected products include GeForce, RTX/Quadro/NVS, and Tesla product lines, including vGPU Manager deployments.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds low-privilege code execution corrupt kernel memory, with potential outcomes of privilege escalation, arbitrary code execution, denial of service, information disclosure and data tampering (CWE-787, CVSS 7.8). The assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H shows low attack complexity and no user interaction, but the attack is strictly local: an attacker must first have a foothold on the host, or on a guest in a vGPU configuration, which confines it to privilege-escalation and sandbox-escape scenarios rather than remote mass exploitation. No public exploit code and no confirmed active exploitation were identified at time of analysis (no public exploit identified at time of analysis), so this is a genuine local privilege-escalation priority despite the absence of exploitation signals, and it warrants prompt patching on endpoint, workstation, and multi-tenant virtual-desktop estates.
A use-after-free (CWE-416) in the NVIDIA GPU Display Driver for Windows and Linux lets a local unprivileged user free and then re-reference a driver-managed memory object, potentially yielding code execution in kernel context, privilege escalation, data tampering, denial of service, and information disclosure. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and affects GeForce, RTX/Quadro/NVS, and Tesla product lines; the 'Guest Driver' tag indicates the vulnerable path may also be reachable from inside a virtualized guest, making guest-to-host or guest-context escalation a relevant scenario. Exploitation requires that the attacker already hold a local foothold with normal user privileges on a host with the affected driver installed and the GPU device interface exposed - there is no remote/network vector - and at time of analysis no public exploit code and no confirmed active exploitation have been identified, so this is a priority local privilege-escalation issue rather than an imminent, opportunistically exploited threat.
Local kernel stack memory disclosure in NVIDIA GPU Display Driver for Windows and Linux allows an attacker who already has low-privilege authenticated code execution on the host to read kernel stack contents such as return addresses and pointers. Affected installations include GeForce, RTX/Quadro/NVS, and Tesla driver configurations, and the independent assessment rates the flaw as AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning high confidentiality impact without confirmed integrity or availability impact. No public exploit is identified at time of analysis, and no CISA KEV active exploitation is reported.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged user to read beyond the bounds of kernel heap memory, producing information disclosure and denial of service, with potential for privilege escalation, code execution, and data tampering if the read primitive is successfully leveraged. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla product families on systems with the vulnerable driver branch installed, and exploitation requires an attacker to already hold local access to the host (per the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N vector, base 7.8), with no user interaction needed. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so exploitation is currently expected to require a motivated local attacker rather than being broadly weaponized.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds a low-privileged execution context on the host read past the bounds of a kernel buffer, exposing kernel memory contents and creating a pathway toward further privilege escalation or data tampering. Exploitation is constrained to the local attack surface: the attacker must already be able to run code on the machine (AV:L, PR:L) and no user interaction or network path is involved, so despite the 7.8 headline score the practical risk is a local privilege/information-disclosure concern rather than a remotely reachable, mass-exploitable flaw. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the affected hardware spans GeForce, RTX/Quadro/NVS, and Tesla products, with an NVIDIA vendor advisory available.
Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer allows a user with standard privileges to trigger an out-of-bounds write in kernel memory, potentially achieving kernel-level code execution, denial of service, information disclosure and data tampering. The affected driver branches span NVIDIA GeForce, RTX/Quadro/NVS and Tesla families on both Windows and Linux, and the 'Guest Driver' tag indicates virtualized/vGPU and guest-VM driver deployments are also in scope, which matters for GPU-accelerated VDI and datacenter estates. Exploitation is constrained to the host: the CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), so an attacker must already have a foothold and the ability to run code as a low-privileged local user; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged local user to trigger an integer overflow in the kernel mode layer, resulting in an out-of-bounds write to GPU memory that can lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. Affected platforms include GeForce, RTX/Quadro/NVS, and Tesla drivers, with the 'Guest Driver' tag indicating that VM guests with GPU access are also in scope for guest-to-host or in-guest escalation. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and the CVSS 3.1 score is 7.8 (AV:L/PR:L/UI:N).
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged user to trigger an incorrect conversion between numeric types in the kernel mode layer, potentially leading to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The vulnerability requires local access and low-level privileges (CVSS vector PR:L) with no user interaction, and it is not remotely exploitable. No public exploit code has been identified at time of analysis, but the risk is materially higher on shared or multi-tenant GPU hosts such as VDI, vGPU, or Tesla datacenter deployments where untrusted users can reach the driver.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows and Linux lets a low-privileged local user trigger an out-of-bounds array access in the kernel mode layer, potentially yielding code execution in kernel context, denial of service, escalation of privileges, information disclosure and data tampering. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), meaning the attack is strictly local and requires only low-privileged authenticated code on the host, with no user interaction and low complexity - so any unprivileged process able to reach the affected kernel-mode interface on a system running GeForce, RTX/Quadro/NVS or Tesla drivers (or a vGPU host reachable from a guest) can attempt it. There is confirmed actively exploited (CISA KEV) status: no - the CVE is not in KEV and no public exploit code has been identified at time of analysis, so early patching is key while exploitation activity has not yet been observed.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows allows a low-privileged local user - or a sandboxed process or guest with access to the driver interface - to trigger a use-after-free in the kernel-mode layer, potentially achieving kernel code execution, privilege escalation, denial of service, information disclosure, or data tampering. The assessed vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) means the attacker must already have code running on a host with an affected NVIDIA driver installed, but needs no user interaction and faces low complexity once local access exists; per the affected CPEs, the GeForce, RTX/Quadro/NVS, and Tesla branches are in scope, and the associated Guest Driver and Virtual GPU Manager tags mean a virtual-GPU guest may also be able to reach the kernel layer. No public exploit code or confirmed active exploitation was identified at the time of analysis, and hosts without an NVIDIA GPU/driver installed are unaffected.
Local code execution, privilege escalation, denial of service, information disclosure, and data tampering are possible on Linux systems running vulnerable NVIDIA GPU Display Drivers (GeForce, RTX/Quadro/NVS, and Tesla branches) because of a type-confusion flaw (CWE-843) in the outdated embedded cryptographic library used by the NGX updater. The assessed profile is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8): an attacker who already holds a low-privileged local account can reach the vulnerable updater code path, with no user interaction required and low complexity, but the flaw is not remotely reachable, so shared and multi-user hosts (VDI, HPC/Tesla compute clusters, and workstations with untrusted local users) are the realistic risk surface. No public exploit code has been identified at time of analysis, and the exact affected and fixed driver versions must be confirmed from NVIDIA's advisory.
Integer overflow in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager can be triggered by a low-privileged user inside a guest VM, causing memory corruption with high confidentiality, integrity, and availability impact. The vulnerability affects vGPU deployments on Windows and Linux hosts across GeForce, RTX/Quadro/NVS, and Tesla driver branches, and successful exploitation could enable code execution, denial of service, privilege escalation, information disclosure, or data tampering. No public exploit code or active exploitation has been identified in the provided intelligence at time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, low-privileged user to drive an out-of-bounds write in the driver's kernel-mode layer by supplying mismatched memory buffers during event buffer setup, with a successful exploit potentially leading to kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The affected code is the Linux kernel-mode component shipped with GeForce, RTX/Quadro/NVS and Tesla driver packages, and the same path can be reached by untrusted code inside a guest VM using the NVIDIA vGPU guest driver on a host running the Virtual GPU Manager. No public exploit code was identified and there is no confirmed active exploitation (CISA KEV) at time of analysis; the bug is local-only, requiring the attacker to already run code with at least low privileges on the host or in a guest, and it is not remotely reachable.
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Unauthenticated remote attackers can tamper with token state and disrupt service availability in NVIDIA AIStore for Linux by sending crafted token-revocation lists to a token-revocation endpoint that performs no authentication check (CVSS 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H). Because the vector shows PR:N and UI:N, no credentials, privileges, or user interaction are needed - any network-reachable deployment of the affected endpoint is directly exploitable, with the only practical limiting factor being firewall or segmentation controls around the AIStore management/control interface. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but the missing authentication control (CWE-306) is the defect itself, so the issue should be treated as a genuine high-priority exposure rather than an inflated score.
Missing authorization in the NVIDIA AIStore ETL management API lets remote, unauthenticated attackers read ETL job information and issue start or stop operations against existing extract-transform-load pipelines by sending crafted GET or POST requests to an AIStore proxy (CVE-2026-65172, CVSS 8.6, CWE-862). Per the assessed vector (AV:N/AC:L/PR:N/UI:N, C:H/I:L/A:L), no credentials or user interaction are required; the practical constraint is network reachability to a proxy that exposes the ETL management API in Linux or Kubernetes deployments. No public exploit code and no confirmed active exploitation were identified at time of analysis, so the immediate risk is driven by exposure of the proxy API rather than by observed attack activity.
Unauthenticated remote attackers can abuse NVIDIA AIStore's experimental HT backend to perform server-side request forgery by supplying a crafted 'original URL' value, causing the AIStore server to issue requests to attacker-chosen destinations and disclose information reachable from the server's network position. The flaw carries a CVSS 3.1 score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N), reflecting no authentication or user interaction requirement and a scope change, with impact confined to confidentiality - integrity and availability are unaffected. There is no public exploit identified at time of analysis, and the practical risk is gated almost entirely on whether the experimental HT backend has been enabled on a network-exposed deployment, since that component is not part of the default AIStore configuration and is only reachable in non-standard setups.
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
Unauthenticated remote attackers can achieve code execution and privilege escalation against NVIDIA AIStore for Linux by injecting arbitrary Kubernetes host-namespace and container security settings into the legacy ETL Kubernetes PodSpec initialization API, rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) because the impact escapes the AIStore workload and extends to the underlying Kubernetes node and cluster. The vector confirms the attack is network-reachable with no privileges or user interaction required, though practical exploitation depends on the legacy ETL/transformation feature being enabled and the ETL API being exposed, and on Kubernetes RBAC and PodSecurity admission being permissive enough for AIStore to actually schedule host-namespaced or privileged pods. At time of analysis there is no confirmed active exploitation (CISA KEV) and no public exploit code identified, but the vendor-reported severity, the scope-changed impact, and CWE-250 (execution with unnecessary privileges) place this in top-priority territory for any cluster running an exposed AIStore ETL endpoint.
Unauthenticated path traversal in the NVIDIA AIStore Promote API on Linux lets a remote attacker read arbitrary files that the AIStore process can access by supplying a crafted absolute source path, resulting in high-confidentiality information disclosure (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Any network-reachable deployment where the Promote endpoint is enabled and functional is at risk, since the vector requires no authentication (PR:N) and no user interaction (UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical blast radius is bounded by the OS privileges of the AIStore process account and by whether the Promote API is exposed beyond trusted internal networks, making this a genuine but moderate-priority issue rather than a critical emergency.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Hash collisions in the inference request cache of NVIDIA Megatron-LM let an attacker who can already submit inference requests tamper with cached data and obtain partial information about other users' cached requests and responses, yielding a CVSS 7.1 impact (AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:H/A:N). Because the cache key relies on a weak hash (CWE-328), success depends on the attacker engineering colliding inputs against an enabled, shared inference cache, which is why the vector rates complexity as high rather than trivial. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; this is a moderate-severity issue rather than a top-tier emergency, and the NVIDIA product-security advisory is the authoritative source for affected builds and fixed versions.
Unauthenticated path traversal in the target-side object rename handler of NVIDIA AIStore on Linux allows a remote attacker who can reach a target (storage) node directly to write files outside the intended storage directory by supplying a crafted rename destination, resulting in arbitrary file creation or overwrite. NVIDIA rates the issue CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-22), with downstream consequences that could include code execution, privilege escalation, information disclosure, data tampering, and denial of service depending on what the overwritten path controls. Exploitation is constrained rather than trivial: the attacker needs network reachability to a target node - not merely the front-end proxy - and must build a traversal payload the rename handler accepts, so exposure is greatest in flat cluster networks or environments where target ports are directly reachable; no public exploit code and no CISA KEV entry were identified at time of analysis.
Server-side request forgery in NVIDIA AIStore for Linux's distributed sort (dsort) component allows remote unauthenticated attackers to make an AIStore node issue outbound HTTP requests to an arbitrary URL by supplying a crafted external key map URL, resulting in disclosure of information from internal or otherwise unreachable services. The CVSS 3.1 base score is 8.6 (High) via AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N, meaning the attack is network reachable, low complexity, requires no privileges and no user interaction, with the impact limited to confidentiality (integrity and availability are unaffected). At time of analysis no public exploit code has been identified, there is no CISA KEV listing for this CVE, and no EPSS score was supplied in the available data.
Stack-based buffer overflow in NVIDIA DALI lets a locally authenticated, low-privileged user who can get a crafted input file processed through a DALI pipeline corrupt memory and potentially achieve code execution, information disclosure, data tampering, or denial of service. Per the assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3 High), exploitation is not remotely reachable: it requires an existing local foothold with at least low privileges plus some form of user interaction, which in practice means a victim or automated process must load attacker-controlled data. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; the practical risk concentrates on multi-tenant or pipeline-automation GPU hosts where untrusted files are routinely fed into DALI. Exact affected versions are unconfirmed because the CPE is a wildcard, so defenders must verify their deployed DALI build against the NVIDIA advisory.
An uncontrolled out-of-bounds read in NVIDIA DALI (Data Loading Library) can be triggered when a low-privileged local user processes specially crafted input through a DALI data-loading or augmentation pipeline (CVSS 3.1 base 7.3, AV:L/AC:L/PR:L/UI:R), resulting in memory disclosure, data tampering, and denial of service. Impact is bounded by the local attack vector and the requirement for both low privileges and user interaction - an unauthenticated remote attacker cannot trigger it directly, and an idle default installation is not exploitable. Exposure is greatest in workflows where DALI ingests untrusted or externally sourced datasets and media; the CPE record (cpe:2.3:a:nvidia:dali:*:*:*:*:*:*:*:*) indicates the issue is not version-scoped in the supplied data, and no public exploit code or CISA KEV entry has been identified at time of analysis.
An uncontrolled out-of-bounds write in NVIDIA DALI (the Data Loading Library used for GPU-accelerated data preprocessing) allows a locally positioned attacker who already holds low-level privileges to corrupt process memory when a DALI pipeline loads or decodes attacker-influenced input such as a crafted image, media file, or dataset record. A successful exploit can produce denial of service, information disclosure, and data tampering, consistent with the vendor rating of 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), which requires local access, low privileges, and user interaction (a victim or process must ingest the malicious data). There is no CISA KEV listing and no public exploit identified at time of analysis, so practical risk is concentrated in multi-tenant training clusters, pipelines consuming externally sourced datasets, and services that accept user-submitted media for GPU preprocessing rather than in default in-house-only deployments.
An uncontrolled out-of-bounds read in NVIDIA DALI is triggered while the library parses attacker-supplied data inside a data-loading pipeline, allowing crafted input to expose process memory contents and crash the workload, which results in information disclosure and denial of service. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:H) the attack is local, requires the attacker to already hold low-level privileges on the host, and critically depends on user interaction - a user or training job must actually run DALI over the malicious sample, so environments that ingest only trusted, internally generated data are effectively not exposed. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); this is a moderate, not top-tier, priority.
Eval injection in NVIDIA Isaac Lab allows a local attacker who can supply crafted input - such as a malicious experiment configuration, task/environment definition, or command-line parameter - to achieve arbitrary code execution, information disclosure, data tampering, and denial of service once a user opens, loads, or runs the content. The flaw is rated CVSS 7.8 (HIGH) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: no privileges are required (PR:N) but the victim must interact with the malicious input (UI:R), the attack path is local (AV:L), and impact is scoped to the invoking user (S:U), so no privilege escalation is implied. The CPE entry is a wildcard with no version boundary and no fixed version is published in the available data, so all Isaac Lab releases should be treated as potentially affected; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Deserialization of untrusted data in NVIDIA Model-Optimizer (CVSS 3.1 base score 7.8) allows an attacker who supplies a crafted model artifact to achieve code execution, data tampering, denial of service, and information disclosure on the machine that loads it. The assessed vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) shows the severity comes from full loss of confidentiality and integrity once the payload runs, but the attacker must first get the victim to open or deserialize the malicious artifact in a local processing environment, so there is no remote, zero-interaction path. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so this is a credible but priority-setting issue for ML/AI pipelines that ingest third-party models rather than an emergency remote-exploitation case.
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.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Out-of-bounds write in the NVIDIA GPU Display Driver for Windows kernel module can let a local, authenticated low-privileged user execute code, escalate privileges, cause denial of service, disclose information, or tamper with data on affected GeForce, RTX/Quadro/NVS, and Tesla systems. Exploitation requires local access to the GPU-equipped Windows host plus a low-privileged account able to reach the kernel module, and the high attack complexity means it is not reliably one-shot; multi-user, VDI, and cloud/virtual-GPU environments are the main risk. No public exploit identified at time of analysis, and CVSS is 7.0 with high confidentiality, integrity, and availability impact.
Denial of service and kernel memory disclosure in the NVIDIA GPU Display Driver for Windows and Linux let a local, low-privileged user who already holds an interactive session on the host force the kernel-mode component to dereference an untrusted pointer, crashing the driver or leaking kernel memory. The flaw is scored CVSS 3.1 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) - a local-only, low-complexity attack requiring low-privilege authenticated access with no user interaction, delivering high confidentiality and availability impact but no integrity or write primitive, so it cannot by itself be chained into privilege escalation or code execution. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); the most exposed deployments are multi-user, VDI, and cloud-GPU hosts where untrusted users share a GPU, since the attacker must first obtain code execution or an interactive session on the GPU host.
An out-of-bounds read in the NVIDIA Display Driver for Windows kernel module allows local attackers to cause denial of service and disclose sensitive kernel memory. Affected products include GeForce, RTX/Quadro/NVS, and Tesla driver lines on Windows; exploitation requires local access with no elevated privileges or user interaction. No public exploit code has been identified, and the vulnerability is not remotely exploitable.
Authenticated low-privileged local users can bypass cryptographic signature verification in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux when the system is under memory pressure, leading to data tampering and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla driver branches on Linux; no public exploit code has been identified at time of analysis. Our assessment rates this as a genuine but bounded-priority local issue because the attacker must reliably induce a low-memory kernel state at the moment of verification, making exploitation opportunistic rather than dependable.
Information disclosure and data tampering can be achieved by a local low-privileged attacker exploiting a missing authorization check in the NVIDIA GPU Display Driver for Windows kernel module. Affected products include the GeForce, RTX/Quadro/NVS, and Tesla driver branches on Windows; exploitation requires local authenticated access (PR:L) and no user interaction (UI:N). No public exploit code or active exploitation has been identified at time of analysis; the CVSS score is 7.3 with scope change (S:C) that amplifies risk in multi-user or cloud-GPU environments.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux can be achieved by an unprivileged local user through the open-source kernel module's DMA-BUF import path, where importing a read-only buffer from another device's DMA-BUF exporter improperly preserves memory access permissions. Successful exploitation can result in code execution, privilege escalation, denial of service, information disclosure, and data tampering, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit identified at time of analysis, and no CISA KEV entry is present in the provided data.
Local privilege escalation and kernel-level code execution in the NVIDIA GPU Display Driver for Windows and Linux, where the kernel-mode layer follows an error-handling path that operates on an improperly initialized resource (CWE-908). The flaw is reachable by an authenticated, low-privileged local user (CVSS 3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) on any host where the affected driver is installed and loaded, granting full confidentiality, integrity, and availability impact within the kernel-mode driver's scope. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); risk is concentrated on shared multi-tenant GPU hosts such as VDI, cloud GPU instances, and vGPU guests where untrusted local users coexist with the driver, and success may be probabilistic because the attacker must reliably trigger the failing error path.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in the NVIDIA GPU Display Driver's open-source kernel module lets an unprivileged local user trigger a use-after-free in the Resource Server map cleanup path via a missing self-reference guard, yielding code execution, privilege escalation, denial of service, information disclosure and data tampering (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, CWE-416). Affected are Windows and Linux hosts running the open-source kernel module variant of the driver, spanning GeForce, RTX/Quadro/NVS and Tesla product lines per the published CPEs; exploitation requires only a normal local account and no user interaction, but is strictly local with no network vector. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical risk is highest in shared or multi-tenant GPU environments (vGPU, VDI, cloud GPU) where gaining kernel-level control of the GPU driver crosses a meaningful tenant boundary.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and potential code execution in NVIDIA GPU Display Driver for Windows and Linux arise from a use-after-free (CWE-416) reachable by a low-privileged local user who can issue a crafted sequence of driver commands. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates confidentiality, integrity, and availability impact as high, with the greatest risk in shared or virtualized GPU deployments where guest-driver or virtual GPU manager isolation may be broken. No public exploit code or confirmed active exploitation is identified in the available data, and EPSS is not provided; exploitation requires local access and construction of the specific command sequence.
Local privilege escalation in NVIDIA Display Driver for Windows allows an authenticated low-privileged user to trigger a stack-based out-of-bounds write in the kernel mode layer, potentially leading to code execution, privilege escalation, and denial of service. Affected systems include Windows hosts with GeForce, RTX/Quadro/NVS, or Tesla drivers, as well as the Guest Driver in virtualized deployments. No public exploit code or active exploitation has been identified at time of analysis, and the flaw requires local access, making it most relevant to shared multi-tenant environments.
An out-of-bounds read in the kernel-mode layer of NVIDIA GPU Display Driver on Windows and Linux allows a local, authenticated unprivileged user to potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. Affected products include GeForce, RTX/Quadro/NVS, and Tesla GPUs, as well as Guest Driver and vGPU Manager deployments. With a CVSS score of 7.8, the vulnerability requires local access and low privileges (CVSS vector AV:L/AC:L/PR:L/UI:N), making it primarily a risk in multi-user or shared-GPU environments; no public exploit has been identified at time of analysis, and patched driver branches are available in NVIDIA security bulletin 5861.
Local privilege escalation in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows an unprivileged local user to bypass read-only memory protection and gain write access to memory the driver marked read-only, which can result in kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering. Exploitation requires the attacker to already hold low-privileged local access on an affected Linux host (CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N, score 7.8) with no user interaction and no network vector; the risk is greatest on shared, multi-tenant vGPU, VDI, and cloud-GPU hosts where crossing the user-to-kernel boundary breaks tenant isolation. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but NVIDIA has published a fix through security bulletin 5861. This is a genuine local privilege-escalation risk rather than an emergency, and it should be prioritized on multi-tenant GPU infrastructure.
Local privilege escalation in NVIDIA Display Driver for Windows and Linux allows an unprivileged local attacker to trigger a use-after-free condition by issuing a crafted sequence of driver commands, potentially achieving code execution, privilege escalation, denial of service, or information disclosure. The vulnerability affects systems with GeForce, RTX/Quadro/NVS, or Tesla GPUs running vulnerable driver versions. No public exploit identified at time of analysis.
Local privilege escalation and memory corruption in NVIDIA GPU Display Driver on Windows and Linux, affecting GeForce, RTX/Quadro/NVS, and Tesla lines. An unprivileged local user can trigger a use-after-free (CWE-416) by issuing a specific sequence of driver commands, leading to potential code execution, privilege escalation, denial of service, or information disclosure. Requires local access and low privileges (AV:L/PR:L) with no user interaction (UI:N); no public exploit identified at time of analysis. Risk is highest in multi-user or shared-GPU environments such as VDI, terminal servers, and cloud/virtualized GPU hosts.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, unprivileged user to trigger a use-after-free condition by issuing a specific sequence of driver commands, potentially leading to code execution, privilege escalation, denial of service, and information disclosure. The vulnerability affects GeForce, RTX/Quadro/NVS, and Tesla GPU drivers, including guest-VM vGPU deployments, and requires local access with low privileges. No public exploit code or confirmed active exploitation has been identified at time of analysis.
Use-after-free in the NVIDIA GPU Display Driver for Linux allows a local, unprivileged user to corrupt driver memory by racing or abusing object lifetime handling, with a successful exploit potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The flaw scores 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is confined to local attackers who already hold an account on the GPU host, with no network vector and no user interaction required. This is a genuine but not emergency-grade issue: no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so realistic exposure is concentrated on shared or multi-tenant GPU systems - VDI desktops, cloud GPU instances, and HPC nodes - where untrusted users share a single driver instance.
An integer underflow (CWE-191) in the kernel-mode component of the NVIDIA GPU Display Driver for Windows lets a local, authenticated low-privileged user corrupt kernel memory in a way that can lead to code execution, privilege escalation, denial of service, information disclosure, or data tampering (CVSS 3.1: 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The issue affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches and is not network-reachable, so an attacker must already be able to run code as a normal user on the host. There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is concentrated on multi-user, VDI and cloud-GPU hosts where an unprivileged tenant shares the same machine as the vulnerable driver, while single-user desktops where the attacker must already hold a foothold face lower marginal risk.
Type confusion in the kernel-mode component of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution to corrupt kernel memory and potentially escalate to SYSTEM, crash the machine (BSOD/DoS), disclose kernel memory, or tamper with data. The issue is rated CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning the attacker must be local and authenticated with low privileges and no user interaction is required, and it affects the GeForce, RTX/Quadro/NVS and Tesla Windows driver branches. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is an access-gated local privilege-escalation risk rather than a remotely reachable mass-exploitation threat.
Local privilege escalation in NVIDIA Display Driver on Windows allows an authenticated low-privileged user to trigger a use-after-free in the kernel-mode driver, potentially enabling code execution with SYSTEM privileges, denial of service, information disclosure, or data tampering. The vulnerability requires local access and high attack complexity (AC:H) due to race conditions or kernel-pool reclamation, making reliable exploitation non-trivial, and it is not known to be actively exploited. The highest risk is in shared multi-user, VDI, or cloud-GPU environments where crossing a trust boundary from low-privileged user to kernel is significant.
Incorrect buffer size calculation in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows allows a local attacker who already holds low-privileged code execution on the host to escalate to kernel-level privileges, with downstream risk of code execution, denial of service, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla data-center, and vGPU/Virtual GPU Manager drivers, and rates CVSS 3.1 base 7.8 (AV:L/AC:L/PR:L/UI:N) - it is strictly local, not remotely triggerable, so exposure is limited to shared workstations, multi-tenant vGPU/VDI environments, and cloud-GPU nodes where an untrusted party can already run code. No public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows allows an authenticated attacker with low-privileged code execution to exploit an integer overflow (CWE-190) in the kernel module, potentially achieving code execution, denial of service, information disclosure, and data tampering. The flaw requires local access (AV:L) and low privileges (PR:L) with no user interaction, affecting systems with GeForce, RTX/Quadro/NVS, or Tesla drivers. No public exploit code or active exploitation has been identified at the time of analysis; the CVSS 3.1 base score is 7.8 (HIGH).
Local code execution and denial of service on Windows systems with affected NVIDIA GPU Display Drivers stem from an integer overflow in the display driver's DIAG escape handler that results in an out-of-bounds write (CWE-787). An unprivileged local user (CVSS PR:L) can trigger the flaw via a device I/O call to the handler; no user interaction is required, and exploitation is confined to the local machine, meaning an attacker must already have a foothold. No public exploit identified at time of analysis (and no CISA KEV entry), but the shared-system impact-multi-user workstations, VDI, and cloud GPU instances-raises the risk profile.
An out-of-bounds write in NVIDIA NVAPI for Windows allows a locally authenticated attacker holding standard user privileges to corrupt memory by invoking NVAPI entry points, potentially leading to code execution, elevation of privileges, information disclosure, denial of service, or data tampering. The flaw affects hosts running the NVIDIA GPU driver package on Windows - including GeForce, RTX/Quadro/NVS, and Tesla driver-equipped systems - with a CVSS 3.1 base score of 7.8 (HIGH) under vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. No public exploit code and no confirmed active exploitation (CISA KEV) have been identified at time of analysis, but the local-only, low-privilege prerequisite makes shared and multi-tenant GPU/VDI hosts the most exposed environment.
Type confusion in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a local low-privileged user (CVSS vector AV:L/AC:L/PR:L/UI:N) who can reach the driver's device-node/ioctl interface to trigger memory corruption with high impact across confidentiality, integrity, and availability, potentially yielding code execution in kernel context, privilege escalation to root, denial of service, information disclosure, and data tampering. The CVSS 3.1 base score of 7.8 reflects a local attack vector paired with uniformly high impacts rather than any remote reachability, and despite the 'RCE' tag in the source metadata the vulnerability is not remotely exploitable. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and no EPSS or CISA KEV signal was provided.
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
Local privilege escalation in NVIDIA GPU Display Driver for Windows (CUDA driver component) allows an authenticated attacker with low privileges to execute arbitrary code by planting a malicious library in an uncontrolled search path. Affected products include GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest driver branches. No public exploit identified at time of analysis; exploitation requires local access and write permissions to a directory resolved by the driver's search path, making it most relevant on shared multi-user or VDI/cloud-GPU hosts.
A type-confusion flaw in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux lets a local, low-privileged user who can open the driver's device nodes and issue ioctls trigger memory corruption by winning a handle-recycle race, yielding kernel-level code execution, privilege escalation, denial of service, information disclosure and data tampering. Affected platforms are the Linux driver branches covering GeForce, RTX/Quadro/NVS, Tesla/data-center GPUs and the vGPU guest driver and Virtual GPU Manager (CVSS 3.1 base 7.8; our independent assessment rates it AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, i.e. 7.0, because the race window makes exploitation timing-sensitive rather than deterministic). This is a local privilege-escalation-class issue with no remote vector: no public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), though it is most consequential on multi-user, VDI and cloud/virtualized GPU hosts where untrusted tenants share a single driver instance.
A NULL pointer dereference in the kernel-mode layer of the NVIDIA GPU Display Driver for Linux allows a locally present, low-privileged authenticated user to crash the driver - and potentially the kernel - by supplying a crafted request to the kernel-mode driver layer (for example via device ioctls). Affected platforms span the GeForce, RTX/Quadro/NVS, and Tesla driver lines on Linux, and the 'Guest Driver' / 'Virtual GPU Manager' tags indicate the vGPU path is also in scope, so a guest session inside a virtualized vGPU deployment is a valid attack position. The vendor claims the flaw 'might' lead to code execution, privilege escalation, information disclosure, and data tampering, but the reliably achievable outcome is a denial-of-service crash; there is no CISA KEV listing, no EPSS score provided, and no public exploit identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to trigger an out-of-bounds write in kernel memory via a crafted ioctl call with an unvalidated buffer size, enabling code execution, privilege escalation, information disclosure, and denial of service. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla drivers, as well as Guest Driver and Virtual GPU Manager components, with highest risk in multi-tenant GPU environments such as VDI and cloud/HPC deployments. No public exploit identified at time of analysis; CVSS 3.1 score is 7.8 (local, low privileges, no user interaction).
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated unprivileged user to trigger a use-after-free in the kernel mode layer, potentially achieving code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw is reachable only by a locally authenticated low-privileged account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) that can issue ioctls to the GPU kernel-mode device interface; there is no remote attack path and no user interaction is required once a foothold exists. The 'Guest Driver' classification makes the issue most consequential in virtualized/vGPU and multi-tenant datacenter environments, where a low-privileged guest can reach the shared GPU driver. No public exploit identified at time of analysis, and the vendor advisory is the authoritative source for fixed driver versions.
Local privilege escalation in NVIDIA's GPU Display Driver (GeForce, RTX/Quadro/NVS, and Tesla, on both Windows and Linux) allows an authenticated low-privileged local user to reach GPU memory belonging to another process, enabling code execution, escalation of privileges, data tampering, denial of service, and information disclosure. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) there is no remote or network path; the flaw is most consequential on shared, multi-user, VDI, or multi-tenant GPU hosts where cross-process GPU memory isolation is the boundary between users and tenants. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the provided vendor reference points to NVIDIA's product security advisory (2026/5861) rather than a fixed driver version named in this data set.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel mode layer allows an authenticated, unprivileged user to trigger a double-free of imported memory state, potentially leading to code execution, denial of service, information disclosure, and data tampering. The flaw requires local access and a low-privilege account; no public exploit code or active exploitation has been identified at time of analysis. The CVSS 3.1 score is 7.8 (HIGH).
Local privilege escalation, code execution, denial of service, and information disclosure in NVIDIA GPU Display Driver on Windows and Linux stem from an integer overflow (CWE-190) in the kernel-mode layer that an unprivileged user can trigger to cause an out-of-bounds write. Exploitation requires local access with an existing low-privilege account (authenticated, PR:L) on a host with an affected GeForce, RTX/Quadro/NVS, or Tesla driver; the CVSS v3.1 base score is 7.8 (High) with a local attack vector (AV:L/AC:L/PR:L/UI:N). No public exploit code or CISA KEV entry was identified at the time of analysis, but the flaw is genuine and actionable for local privilege escalation if the vulnerable driver interface is reachable.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows an unprivileged local user to corrupt kernel memory, which can lead to code execution in the kernel, privilege escalation, denial of service, information disclosure, or data tampering. Systems running GeForce, RTX/Quadro/NVS, or Tesla driver packages on either operating system are affected; per the CVSS vector (AV:L, PR:L, UI:N) the flaw is reachable only by a user who already has local code execution on the host, making it a local privilege-escalation primitive rather than a remote entry point. No public exploit has been identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Linux stems from a missing authorization check in the kernel mode layer, allowing an unprivileged local user to modify privileged configuration and potentially achieve code execution, escalation of privileges, denial of service, information disclosure, and data tampering. Exploitation requires a pre-existing local low-privileged foothold (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), such as an unprivileged account on a host or inside a guest VM using the NVIDIA guest driver or Virtual GPU Manager, so this is an escalation primitive rather than a remote initial-access vector. No public exploit code is identified and no CISA KEV active exploitation is confirmed at time of analysis, but the high confidentiality, integrity, and availability impacts and broad affected driver families make patching a priority.
Use-after-free in the NVIDIA GPU Display Driver kernel mode layer (Windows and Linux) lets a local user who already holds low-privileged code execution on the host trigger a memory-corruption condition inside the kernel driver, with the potential for code execution, privilege escalation, information disclosure, data tampering, and denial of service. Affected platforms span consumer and professional GPU lines (GeForce, RTX/Quadro/NVS, Tesla) as well as the vGPU components, where a malicious or compromised guest can exercise the vulnerable path through the Guest Driver and Virtual GPU Manager. The attack is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, score 7.8), requires no user interaction and no non-default configuration beyond having the driver installed, and there is no public exploit identified at time of analysis - no KEV entry and no proof-of-concept code is referenced in the available data.
Local privilege escalation in NVIDIA GPU Display Drivers for Windows (GeForce, RTX/Quadro/NVS, Tesla, and vGPU) allows an unprivileged local user to execute code in kernel mode by supplying an untrusted pointer that the driver dereferences without validation. Affected hosts include multi-user and virtualized Windows systems with default driver installations, where exploitation can lead to escalation to SYSTEM, denial of service, information disclosure, and data tampering. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; the CVSS 3.1 base score is 7.8 (High).
A locally-triggered out-of-bounds write in the NVIDIA GPU Display Driver kernel-mode layer lets an attacker who already holds low-level privileges on a Windows or Linux host corrupt kernel memory, with the potential for code execution in kernel context, escalation of privileges, denial of service, information disclosure and data tampering. The affected driver ships by default across the GeForce, RTX/Quadro/NVS, Tesla and Virtual GPU Manager product lines, so any host with a current NVIDIA driver installed is in scope, but exploitation is not remote: an attacker must first obtain code execution on the target (an authenticated local user, a compromised low-privileged process, or sandboxed code with driver access) and then develop a reliable kernel corruption exploit. CVE-2026-47548 carries a vendor/NVD CVSS 3.1 vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8, High); no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
Local attackers with low-privileged code execution can trigger an out-of-bounds read (CWE-125) in the kernel-mode layer of the NVIDIA GPU Display Driver on Windows and Linux, which may lead to escalation of privileges, code execution, denial of service, information disclosure, and data tampering. This locally exploitable flaw (CVSS 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) affects GeForce, RTX/Quadro/NVS, Tesla, and Virtual GPU Manager products, and no public exploit has been identified at the time of analysis. A vendor advisory with remediation guidance is available from NVIDIA via its product security page.
Integer underflow in the kernel-mode layer of NVIDIA GPU Display Driver for Windows and Linux allows a local attacker with low privileges to potentially achieve code execution, denial of service, privilege escalation, information disclosure, and data tampering. The flaw affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Manager products, and exploitation requires local access (CVSS AV:L) with no user interaction (UI:N) but low privileges (PR:L). No public exploit code has been identified at time of analysis, and there is no indication of active exploitation.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged authenticated user to corrupt kernel memory, with the potential to escalate privileges to kernel-level code execution, crash the system (denial of service), disclose information, or tamper with data. The flaw rates CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires pre-existing code execution as a standard user on a host with the driver loaded, but no user interaction and no non-default configuration; the vulnerable kernel-mode layer ships and loads by default once the driver is installed. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, but the affected GeForce, RTX/Quadro/NVS, and Tesla product families are extremely widely deployed, making this a genuine high-priority patch-management item rather than an emergency.
Local attackers with low privileges can exploit an uninitialized pointer access flaw (CWE-824) in the firmware of NVIDIA Display Driver for Windows and Linux to achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering. The vulnerability requires local access (AV:L) and authenticated low-privilege credentials (PR:L); no public exploit identified at time of analysis. Affected products include GeForce, RTX/Quadro/NVS, and Tesla product lines, including vGPU Manager deployments.
An out-of-bounds write in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds low-privilege code execution corrupt kernel memory, with potential outcomes of privilege escalation, arbitrary code execution, denial of service, information disclosure and data tampering (CWE-787, CVSS 7.8). The assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H shows low attack complexity and no user interaction, but the attack is strictly local: an attacker must first have a foothold on the host, or on a guest in a vGPU configuration, which confines it to privilege-escalation and sandbox-escape scenarios rather than remote mass exploitation. No public exploit code and no confirmed active exploitation were identified at time of analysis (no public exploit identified at time of analysis), so this is a genuine local privilege-escalation priority despite the absence of exploitation signals, and it warrants prompt patching on endpoint, workstation, and multi-tenant virtual-desktop estates.
A use-after-free (CWE-416) in the NVIDIA GPU Display Driver for Windows and Linux lets a local unprivileged user free and then re-reference a driver-managed memory object, potentially yielding code execution in kernel context, privilege escalation, data tampering, denial of service, and information disclosure. The flaw is rated CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and affects GeForce, RTX/Quadro/NVS, and Tesla product lines; the 'Guest Driver' tag indicates the vulnerable path may also be reachable from inside a virtualized guest, making guest-to-host or guest-context escalation a relevant scenario. Exploitation requires that the attacker already hold a local foothold with normal user privileges on a host with the affected driver installed and the GPU device interface exposed - there is no remote/network vector - and at time of analysis no public exploit code and no confirmed active exploitation have been identified, so this is a priority local privilege-escalation issue rather than an imminent, opportunistically exploited threat.
Local kernel stack memory disclosure in NVIDIA GPU Display Driver for Windows and Linux allows an attacker who already has low-privilege authenticated code execution on the host to read kernel stack contents such as return addresses and pointers. Affected installations include GeForce, RTX/Quadro/NVS, and Tesla driver configurations, and the independent assessment rates the flaw as AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, meaning high confidentiality impact without confirmed integrity or availability impact. No public exploit is identified at time of analysis, and no CISA KEV active exploitation is reported.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux allows a local, low-privileged user to read beyond the bounds of kernel heap memory, producing information disclosure and denial of service, with potential for privilege escalation, code execution, and data tampering if the read primitive is successfully leveraged. The flaw affects GeForce, RTX/Quadro/NVS, and Tesla product families on systems with the vulnerable driver branch installed, and exploitation requires an attacker to already hold local access to the host (per the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N vector, base 7.8), with no user interaction needed. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so exploitation is currently expected to require a motivated local attacker rather than being broadly weaponized.
An out-of-bounds read in the kernel-mode layer of the NVIDIA GPU Display Driver for Windows and Linux lets a local attacker who already holds a low-privileged execution context on the host read past the bounds of a kernel buffer, exposing kernel memory contents and creating a pathway toward further privilege escalation or data tampering. Exploitation is constrained to the local attack surface: the attacker must already be able to run code on the machine (AV:L, PR:L) and no user interaction or network path is involved, so despite the 7.8 headline score the practical risk is a local privilege/information-disclosure concern rather than a remotely reachable, mass-exploitable flaw. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the affected hardware spans GeForce, RTX/Quadro/NVS, and Tesla products, with an NVIDIA vendor advisory available.
Local privilege escalation in the NVIDIA GPU Display Driver kernel-mode layer allows a user with standard privileges to trigger an out-of-bounds write in kernel memory, potentially achieving kernel-level code execution, denial of service, information disclosure and data tampering. The affected driver branches span NVIDIA GeForce, RTX/Quadro/NVS and Tesla families on both Windows and Linux, and the 'Guest Driver' tag indicates virtualized/vGPU and guest-VM driver deployments are also in scope, which matters for GPU-accelerated VDI and datacenter estates. Exploitation is constrained to the host: the CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), so an attacker must already have a foothold and the ability to run code as a low-privileged local user; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged local user to trigger an integer overflow in the kernel mode layer, resulting in an out-of-bounds write to GPU memory that can lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. Affected platforms include GeForce, RTX/Quadro/NVS, and Tesla drivers, with the 'Guest Driver' tag indicating that VM guests with GPU access are also in scope for guest-to-host or in-guest escalation. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and the CVSS 3.1 score is 7.8 (AV:L/PR:L/UI:N).
Local privilege escalation in NVIDIA GPU Display Driver for Windows and Linux allows a low-privileged user to trigger an incorrect conversion between numeric types in the kernel mode layer, potentially leading to code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The vulnerability requires local access and low-level privileges (CVSS vector PR:L) with no user interaction, and it is not remotely exploitable. No public exploit code has been identified at time of analysis, but the risk is materially higher on shared or multi-tenant GPU hosts such as VDI, vGPU, or Tesla datacenter deployments where untrusted users can reach the driver.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows and Linux lets a low-privileged local user trigger an out-of-bounds array access in the kernel mode layer, potentially yielding code execution in kernel context, denial of service, escalation of privileges, information disclosure and data tampering. The assessed CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8), meaning the attack is strictly local and requires only low-privileged authenticated code on the host, with no user interaction and low complexity - so any unprivileged process able to reach the affected kernel-mode interface on a system running GeForce, RTX/Quadro/NVS or Tesla drivers (or a vGPU host reachable from a guest) can attempt it. There is confirmed actively exploited (CISA KEV) status: no - the CVE is not in KEV and no public exploit code has been identified at time of analysis, so early patching is key while exploitation activity has not yet been observed.
Local privilege escalation in the NVIDIA GPU Display Driver for Windows allows a low-privileged local user - or a sandboxed process or guest with access to the driver interface - to trigger a use-after-free in the kernel-mode layer, potentially achieving kernel code execution, privilege escalation, denial of service, information disclosure, or data tampering. The assessed vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) means the attacker must already have code running on a host with an affected NVIDIA driver installed, but needs no user interaction and faces low complexity once local access exists; per the affected CPEs, the GeForce, RTX/Quadro/NVS, and Tesla branches are in scope, and the associated Guest Driver and Virtual GPU Manager tags mean a virtual-GPU guest may also be able to reach the kernel layer. No public exploit code or confirmed active exploitation was identified at the time of analysis, and hosts without an NVIDIA GPU/driver installed are unaffected.
Local code execution, privilege escalation, denial of service, information disclosure, and data tampering are possible on Linux systems running vulnerable NVIDIA GPU Display Drivers (GeForce, RTX/Quadro/NVS, and Tesla branches) because of a type-confusion flaw (CWE-843) in the outdated embedded cryptographic library used by the NGX updater. The assessed profile is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8): an attacker who already holds a low-privileged local account can reach the vulnerable updater code path, with no user interaction required and low complexity, but the flaw is not remotely reachable, so shared and multi-user hosts (VDI, HPC/Tesla compute clusters, and workstations with untrusted local users) are the realistic risk surface. No public exploit code has been identified at time of analysis, and the exact affected and fixed driver versions must be confirmed from NVIDIA's advisory.
Integer overflow in the kernel-mode layer of NVIDIA vGPU Virtual GPU Manager can be triggered by a low-privileged user inside a guest VM, causing memory corruption with high confidentiality, integrity, and availability impact. The vulnerability affects vGPU deployments on Windows and Linux hosts across GeForce, RTX/Quadro/NVS, and Tesla driver branches, and successful exploitation could enable code execution, denial of service, privilege escalation, information disclosure, or data tampering. No public exploit code or active exploitation has been identified in the provided intelligence at time of analysis.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux allows an authenticated, low-privileged user to drive an out-of-bounds write in the driver's kernel-mode layer by supplying mismatched memory buffers during event buffer setup, with a successful exploit potentially leading to kernel code execution, denial of service, privilege escalation, information disclosure, and data tampering (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The affected code is the Linux kernel-mode component shipped with GeForce, RTX/Quadro/NVS and Tesla driver packages, and the same path can be reached by untrusted code inside a guest VM using the NVIDIA vGPU guest driver on a host running the Virtual GPU Manager. No public exploit code was identified and there is no confirmed active exploitation (CISA KEV) at time of analysis; the bug is local-only, requiring the attacker to already run code with at least low privileges on the host or in a guest, and it is not remotely reachable.