dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-42261

HIGH · 7.8 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NVIDIA vGPU software contains a vulnerability in the Virtual GPU Manager (vGPU plugin), where an input index is not validated, which may lead to buffer overrun, which in turn may cause data tampering, information disclosure, or denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA vGPU Manager contains a buffer overflow vulnerability in the vGPU plugin due to unvalidated input index handling. When an attacker provides an out-of-bounds index, the manager can write beyond allocated buffer boundaries, potentially allowing data tampering, information disclosure, or denial of service.

MitigationApply the NVIDIA vGPU software patch when released. In the interim, restrict access to the hypervisor and vGPU management interfaces to trusted, authorized personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gpu Display DriverApplication
Affected:>= 470, < 470.161.03>= 510, < 510.108.03>= 450, < 450.216.04
Virtual GpuApplication
Affected:< 11.11>= 12.0, < 13.6>= 14.0, < 14.4
Cloud GamingApplication
Affected:< 525.60.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed NVIDIA vGPU software
    Run 'nvidia-smi' or check installed packages via package manager (dpkg/rpm) for nvidia-vgpu, nvidia-driver, or nvidia-vgpu-software packages. On hypervisors, check vGPU manager service version via 'nvvgpu' daemon or hypervisor-specific tools.
    Affected if NVIDIA vGPU Manager, GPU Display Driver, or NVIDIA Cloud Gaming software is present on the system
  2. Determine installed version of NVIDIA GPU Display Driver
    Run 'nvidia-smi' and check the Driver Version field, or query 'nvcc --version' if CUDA is installed, or check /usr/bin/nvidia-smi directly.
    Affected if Driver version is 450.x.x, 470.x.x, 510.x.x, or any version between the affected ranges (450 to 450.216.04, 470 to 470.161.03, or 510 to 510.108.03)
  3. Determine installed version of NVIDIA vGPU software
    Check vGPU Manager version via hypervisor-specific commands (e.g., virsh list, VMware esxcli, or Xen xl list) or check installed package version for nvidia-vgpu packages.
    Affected if vGPU software version is below 11.11, between 12.0-13.6, or between 14.0-14.4
  4. Determine installed version of NVIDIA Cloud Gaming
    Check installed package version for nvidia-cloud-gaming or nvidia-gaming packages via package manager, or query the gaming service version if running.
    Affected if Cloud Gaming version is below 525.60.12

Your environment is affected if NVIDIA vGPU Manager, GPU Display Driver (versions 450 to 450.216.04, 470 to 470.161.03, or 510 to 510.108.03), vGPU software (versions <11.11, 12.0-13.6, or 14.0-14.4), or Cloud Gaming (<525.60.12) is installed and the vGPU plugin feature is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.11 / 13.6 / 14.4 or later
Fixed in 11.1113.614.4
Interim mitigation

Apply the NVIDIA vGPU software patch when released. In the interim, restrict access to the hypervisor and vGPU management interfaces to trusted, authorized personnel only.

Recommended fix High confidence

GPU Display Driver: 470.161.03, 510.108.03, or 450.216.04 | Virtual GPU: 11.11, 13.6, or 14.4 | Cloud Gaming: 525.60.12

  1. 1. Identify the NVIDIA product in use (GPU Display Driver, Virtual GPU, or Cloud Gaming) and the currently installed version using nvidia-smi or system inventory
  2. 2. For GPU Display Driver: Upgrade to version 470.161.03 (if using 470.x), 510.108.03 (if using 510.x), or 450.216.04 (if using 450.x)
  3. 3. For Virtual GPU: Upgrade to version 11.11 (if using pre-12.0), 13.6 (if using 12.x-13.x), or 14.4 (if using 14.x)
  4. 4. For Cloud Gaming: Upgrade to version 525.60.12 or later
  5. 5. After upgrade, verify the installed version matches the target fixed release
  6. 6. Reboot the system as required by the NVIDIA driver installation
Caveat NVIDIA driver upgrades may require system reboot; ensure compatibility with guest VMs for vGPU deployments before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data