dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-34683

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
57/100
Remediation priority · Elevated
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 kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape, where a null-pointer dereference occurs, which may lead to 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 GPU Display Driver for Windows contains a null-pointer dereference vulnerability in the kernel mode layer handler for DxgkDdiEscape (nvlddmkm.sys). An attacker could trigger this vulnerability through specially crafted calls to the graphics kernel interface, potentially causing a denial of service via system crash.

MitigationApply the NVIDIA driver update that addresses CVE-2022-34683. Prioritize patching systems running vulnerable GPU driver versions, particularly those exposed to untrusted graphics workloads.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Confirm NVIDIA GPU driver is present
    Check for the existence of nvlddmkm.sys in the Windows system directory (C:\Windows\System32\drivers\) or look for NVIDIA GPU in Device Manager under Display adapters.
    Affected if The NVIDIA kernel mode driver (nvlddmkm.sys) is installed.
  2. Retrieve installed driver version
    Open Device Manager, expand Display adapters, right-click the NVIDIA GPU, select Properties, go to the Driver tab, and note the Driver Version string. Alternatively, run 'nvlist.exe' if available, or check the driver file properties of nvlddmkm.sys.
    Affected if A driver version is found on the system.
  3. Check Virtual GPU version against affected ranges
    If running NVIDIA Virtual GPU (vGPU) software, compare the installed version to: versions less than 11.11, versions 13.0 through 13.5.x, or versions 14.0 through 14.3.x.
    Affected if The Virtual GPU version falls into any of these ranges: < 11.11, >= 13.0 and < 13.6, or >= 14.0 and < 14.4.
  4. Check Cloud Gaming version against affected ranges
    If running NVIDIA Cloud Gaming (formerly GeForce NOW), compare the installed version to versions less than 527.27.
    Affected if The Cloud Gaming driver version is lower than 527.27.
  5. Verify DxgkDdiEscape handler is in use
    This is a kernel-level vulnerability in the graphics interface handler. The vulnerability triggers through graphics API calls (DirectX/OpenGL) that exercise the DxgkDdiEscape escape handler. No specific user configuration needs to be enabled; the flaw is present in the driver code itself.
    Affected if The vulnerable nvlddmkm.sys driver version is loaded and handling graphics operations.

The system is affected if it runs any version of NVIDIA Virtual GPU (vGPU) in ranges < 11.11, >= 13.0 to < 13.6, or >= 14.0 to < 14.4; or NVIDIA Cloud Gaming with driver version < 527.27.

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 that addresses CVE-2022-34683. Prioritize patching systems running vulnerable GPU driver versions, particularly those exposed to untrusted graphics workloads.

Recommended fix High confidence

Virtual GPU: 11.11, 13.6, or 14.4 (whichever branch applicable); Cloud Gaming: 527.27

  1. 1. Identify the NVIDIA product in use (Virtual GPU or Cloud Gaming)
  2. 2. For Virtual GPU: Upgrade to version 11.11 or later, 13.6 or later, or 14.4 or later depending on the current branch
  3. 3. For Cloud Gaming: Upgrade to version 527.27 or later
  4. 4. Download the appropriate driver from the official NVIDIA website or enterprise distribution channel
  5. 5. Uninstall the current NVIDIA display driver via Windows Device Manager or the NVIDIA uninstaller
  6. 6. Restart the system
  7. 7. Install the new driver package and restart again to ensure kernel mode components load properly
Caveat Driver updates may require CUDA or other NVIDIA software toolkit compatibility checks; ensure workloads are tested after upgrade

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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