dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-34669

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 in the user mode layer, where an unprivileged regular user can access or modify system files or other files that are critical to the application, 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 a vulnerability in the user mode layer where an unprivileged regular user can access or modify system files or other files critical to the application, potentially leading to code execution, denial of service, privilege escalation, information disclosure, or data tampering.

MitigationApply the NVIDIA driver update/patch for CVE-2022-34669 as soon as feasible; prioritize systems with untrusted users or network exposure given the high-severity local privilege escalation risk.

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
Cloud GamingApplication
Affected:< 527.27

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 NVIDIA GPU driver product type
    Check if the system is running NVIDIA Virtual GPU (vGPU) or NVIDIA Cloud Gaming by reviewing installed NVIDIA software components or checking system information about the GPU driver package.
    Affected if The system has NVIDIA Virtual GPU or NVIDIA Cloud Gaming software installed.
  2. Locate installed NVIDIA driver version
    Open Windows Device Manager, expand Display adapters, right-click the NVIDIA GPU, select Properties, go to the Driver tab, and note the Driver Version string.
    Affected if A driver version is displayed.
  3. Compare version against affected ranges for Virtual GPU
    If using Virtual GPU, compare the installed driver version to the affected ranges: < 11.11, >= 13.0 and < 13.6, or >= 14.0 and < 14.4.
    Affected if The installed Virtual GPU version falls into any of these ranges.
  4. Compare version against affected ranges for Cloud Gaming
    If using Cloud Gaming, compare the installed driver version to the affected range: < 527.27.
    Affected if The installed Cloud Gaming version is less than 527.27.
  5. Verify user mode driver is loaded
    Check that the NVIDIA user mode driver components are active by looking for nvidia.exe or nvlddmkm.sys in running processes or loaded drivers.
    Affected if The NVIDIA user mode driver is actively running.

A system is affected if it runs NVIDIA Virtual GPU in versions below 11.11, 13.0-13.5, or 14.0-14.3, or NVIDIA Cloud Gaming below version 527.27, with the user mode driver loaded.

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 driver update/patch for CVE-2022-34669 as soon as feasible; prioritize systems with untrusted users or network exposure given the high-severity local privilege escalation risk.

Recommended fix High confidence

Virtual GPU: 11.11, 13.6, or 14.4 (depending on branch); Cloud Gaming: 527.27

  1. Identify the current NVIDIA GPU Display Driver version installed on the Windows system by opening NVIDIA Control Panel or checking Programs and Features
  2. For Virtual GPU customers: Determine which version branch is currently in use (11.x, 13.x, or 14.x)
  3. Download the appropriate fixed driver version from NVIDIA's official website or enterprise distribution channels
  4. For Virtual GPU: Upgrade to version 11.11 or later for 11.x branch, 13.6 or later for 13.x branch, or 14.4 or later for 14.x branch
  5. For Cloud Gaming: Upgrade to version 527.27 or later
  6. Uninstall the current driver completely before installing the new version to ensure clean installation
  7. Restart the system after driver installation completes
  8. Verify the driver version after restart to confirm the fix is applied
Caveat Ensure the driver version is compatible with your GPU hardware and virtualization platform before upgrading; test in non-production environment first

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

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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