Gpu Display DriverApplication · Nvidia

CVE-2022-42262

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

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

dbcve analysis · moderate confidence

NVIDIA vGPU Manager contains a buffer overflow vulnerability in the vGPU plugin where an input index is not validated before use, allowing an attacker to write beyond allocated buffer boundaries. This could enable data tampering, information disclosure from memory contents, or denial of service through crash or corruption.

MitigationApply NVIDIA's vendor patch for CVE-2022-42262 when released; until then, restrict access to vGPU management interfaces and hypervisor administrative functions to trusted administrators only.

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

Affected products & versions

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

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?

dbcve checks

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

Identify installed NVIDIA driver or vGPU software version

Run 'nvidia-smi' or check the installed NVIDIA package version using the system's package manager (e.g., 'dpkg -l | grep nvidia' on Debian/Ubuntu, 'rpm -qa | grep nvidia' on RHEL/CentOS, or check Windows registry at HKLM\SOFTWARE\NVIDIA Corporation\Installer2').

Affected if The installed version falls within any of these ranges: GPU Display Driver versions 470.x before 470.161.03, 510.x before 510.108.03, or 450.x before 450.216.04; Virtual GPU versions before 11.11, 12.0-13.x before 13.6, or 14.0-14.x before 14.4; Cloud Gaming versions before 525.60.12.
Confirm vGPU functionality is in use

Check if the system is configured as a hypervisor (VMware ESXi, Citrix Hypervisor, or Microsoft Hyper-V) with vGPU devices assigned to virtual machines, or run 'nvidia-smi -q' and look for vGPU-related information in the output.

Affected if The system is running a hypervisor with vGPU plugin enabled and vGPU virtual devices are configured for guest virtual machines.
Check vGPU plugin status

On supported hypervisors, use hypervisor-specific commands: for VMware ESXi, run 'esxcli system module list' and look for nvidia module status; for Citrix Hypervisor, check 'xl dmesg' or xe CLI for nvidia vgpu plugin; for Hyper-V, check Hyper-V manager for vGPU assignment status.

Affected if The nvidia-vgpu or vGPU plugin module is loaded and active on the hypervisor.
Review vGPU configuration for index-based settings

Examine vGPU configuration files or virtual machine settings where vGPU profiles are assigned. Look for any configuration that specifies vGPU device indices or slot assignments. On ESXi, check VM configuration files for vgpu= settings; on Xen/Citrix, check xe vgpu-create output.

Affected if vGPU profiles with specific device indices are configured and assigned to virtual machines, indicating the vulnerable code path could be reached.

A system is affected if it runs any NVIDIA vGPU software version within the affected ranges AND has vGPU plugin enabled with vGPU devices configured for virtual machines.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 11.11 / 13.6 / 14.4 or later

Fixed in 11.1113.614.4

Interim mitigation

Apply NVIDIA's vendor patch for CVE-2022-42262 when released; until then, restrict access to vGPU management interfaces and hypervisor administrative functions to trusted administrators only.

Recommended fix High confidence

GPU Display Driver: 450.216.04+ (450 branch), 470.161.03+ (470 branch), 510.108.03+ (510 branch) | vGPU: 11.11+ (11.x), 13.6+ (12.x-13.x), 14.4+ (14.x) | Cloud Gaming: 525.60.12+

1. Identify the current NVIDIA driver or vGPU software version by running nvidia-smi or checking the installed package
2. Determine which product category applies: GPU Display Driver, Virtual GPU (vGPU), or Cloud Gaming
3. For GPU Display Driver: note the driver branch (450.x, 470.x, or 510.x) and upgrade to the minimum fixed version for that branch
4. For Virtual GPU: identify the vGPU version (e.g., 11.x, 12.x, 13.x, or 14.x) and upgrade to the minimum fixed version for that release line
5. For Cloud Gaming: upgrade to version 525.60.12 or later
6. Obtain the appropriate fixed driver/software from NVIDIA's official website or download portal
7. Follow NVIDIA's standard installation procedure for the specific product (bare-metal driver install or vGPU manager deployment)
8. Reboot the system as required after installation

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

Fix this in Gpu Display Driver Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing10.0 h
Review / QA3.0 h

22.0 hours of engineering $3,720

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-42262 — 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

Primary sources

nvidia.custhelp.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-42262?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 11.11 / 13.6 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Gpu Display Driver

Remediation

A high-priority fix

Fix this in Gpu Display Driver 22 hrs · Moderate

Typical engagement from $3,720

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-42262 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References