dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-42267

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 GPU Display Driver for Windows contains a vulnerability where a regular user can cause an out-of-bounds read, which may lead to code execution, denial of service, escalation of privileges, information disclosure, or data tampering.

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 GPU Display Driver for Windows contains an out-of-bounds read vulnerability that can be triggered by a regular (non-privileged) user. This memory safety flaw may lead to code execution, denial of service, privilege escalation, information disclosure, or data tampering, representing a significant security risk in kernel-adjacent driver code.

MitigationApply the NVIDIA security patch for this vulnerability by updating the GPU display driver to a patched version. Until patched, limit local user access to systems with affected GPUs and monitor for indicators of exploitation.

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
Virtual GpuApplication
Affected:< 11.11>= 13.0, < 13.6>= 14.0, < 14.4

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. Verify NVIDIA GPU hardware presence
    Open Device Manager, expand 'Display adapters', and confirm an NVIDIA GPU is listed. Alternatively, run 'nvidia-smi' from command line if available.
    Affected if No NVIDIA GPU is found in the system, the driver vulnerability does not apply.
  2. Identify NVIDIA Virtual GPU software installation
    Open 'Programs and Features' in Windows Control Panel and look for NVIDIA virtual GPU software such as 'NVIDIA vGPU Manager', 'NVIDIA GRID vGPU', or similar NVIDIA virtualization products.
    Affected if NVIDIA Virtual GPU software is not installed, this specific CVE does not apply to the system.
  3. Determine installed NVIDIA vGPU software version
    In Programs and Features, right-click the NVIDIA vGPU entry and select Properties, or check the version shown in the installer entry. Alternatively, check the driver version in Device Manager under the NVIDIA GPU properties, Details tab, Driver version.
    Affected if The installed version matches the affected ranges: any version before 11.11, or between 13.0 and 13.5.x, or between 14.0 and 14.3.x.
  4. Confirm user-level access to GPU
    Verify that non-privileged users have the ability to interact with the NVIDIA driver. This is default behavior in Windows where any logged-on user can access display driver functionality.
    Affected if Non-privileged users can access the system and the affected vGPU software version is installed, the vulnerability is exploitable.

A system is affected if it has NVIDIA Virtual GPU software installed with a version matching < 11.11, >= 13.0 and < 13.6, or >= 14.0 and < 14.4, and non-privileged users have access to the system.

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 security patch for this vulnerability by updating the GPU display driver to a patched version. Until patched, limit local user access to systems with affected GPUs and monitor for indicators of exploitation.

Recommended fix Moderate confidence

Minimum fixed versions: 11.11, 13.6, or 14.4 depending on version branch

  1. Identify the currently installed NVIDIA Virtual GPU driver version on the Windows system
  2. Determine which version branch the current installation belongs to (11.x, 13.x, or 14.x)
  3. Download the appropriate fixed NVIDIA Virtual GPU driver from the NVIDIA licensing portal or official support channels
  4. Upgrade to version 11.11 or later if currently on a version before 11.11
  5. Upgrade to version 13.6 or later if currently on version 13.0 through 13.5.x
  6. Upgrade to version 14.4 or later if currently on version 14.0 through 14.3.x
  7. Restart the system after applying the driver update
  8. Verify the installed driver version matches the recommended fixed version
Caveat Driver updates may require application compatibility testing; ensure backup of current configuration

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

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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