dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-34678

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 and Linux contains a vulnerability in the kernel mode layer, where an unprivileged user can cause a null-pointer dereference, 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 and Linux contains a null-pointer dereference vulnerability in the kernel mode layer. An unprivileged user can trigger this flaw, causing a kernel panic or system crash resulting in denial of service.

MitigationApply the NVIDIA driver update or patch provided by NVIDIA for this vulnerability. For systems where immediate patching is not possible, consider restricting user access to GPU-intensive operations or implementing monitoring for kernel-mode crashes.

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>= 12.0, < 13.6>= 14.0, < 14.4>= 13.0, < 13.6
Cloud GamingApplication
Affected:< 525.60.11< 525.60.12< 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. Identify the NVIDIA product
    Determine if the system is running NVIDIA Virtual GPU (vGPU) or NVIDIA Cloud Gaming. On Linux, check /proc/driver/nvidia/version or use nvidia-smi. On Windows, check Device Manager under Display adapters.
    Affected if The product is neither Virtual GPU nor Cloud Gaming (this CVE does not apply to standalone GeForce/Quadro drivers based on the affected products listed).
  2. Check the driver version on Virtual GPU
    Run nvidia-smi -q | grep -i "Driver Version" or check the vGPU manager version. For vGPU software, this is typically the version of the vGPU Manager package installed on the hypervisor.
    Affected if The driver version is less than 11.11, OR between 12.0 and 13.6 (inclusive of 12.0, exclusive of 13.6), OR between 14.0 and 14.4 (inclusive of 14.0, exclusive of 14.4).
  3. Check the driver version on Cloud Gaming
    Run nvidia-smi -q | grep -i "Driver Version" on the gaming instance or check the NVIDIA Gaming Gateway/Server driver version.
    Affected if The driver version is less than 525.60.11, OR less than 525.60.12, OR less than 527.27 (the exact version depends on the specific Cloud Gaming release in use).
  4. Verify kernel mode driver is loaded
    On Linux, check if the nvidia kernel module is loaded via lsmod | grep nvidia. On Windows, check that the NVIDIA Display Driver kernel-mode components are installed via Device Manager or sc query nvlddmkm.
    Affected if The kernel mode driver is loaded and running - the vulnerability triggers when the driver is active, causing null pointer dereference in kernel layer.

You are affected if you are running NVIDIA Virtual GPU or Cloud Gaming with a driver version matching the ranges above AND the NVIDIA kernel mode driver is loaded and active.

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 or patch provided by NVIDIA for this vulnerability. For systems where immediate patching is not possible, consider restricting user access to GPU-intensive operations or implementing monitoring for kernel-mode crashes.

Recommended fix Moderate confidence

Virtual GPU: >= 11.11, >= 13.6, or >= 14.4 depending on branch; Cloud Gaming: >= 527.27

  1. 1. Identify the NVIDIA product in use: Virtual GPU or Cloud Gaming
  2. 2. For Virtual GPU users: Upgrade to version 11.11 or later for the 11.x branch, 13.6 or later for the 12.x/13.x branch, or 14.4 or later for the 14.x branch
  3. 3. For Cloud Gaming users: Upgrade to version 527.27 or later
  4. 4. Download the appropriate driver from the official NVIDIA website or your enterprise software distribution channel
  5. 5. Follow standard NVIDIA driver installation procedures for your operating system (Windows or Linux)
  6. 6. Reboot the system after installation to ensure the new kernel mode driver loads properly
  7. 7. Verify the installed driver version matches the target fixed release using nvidia-smi or driver information utilities
Caveat Standard NVIDIA driver upgrade risks apply: ensure compatibility with your hypervisor/platform version for Virtual GPU, and test in staging for production environments

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
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,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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