dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-34679

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 Linux contains a vulnerability in the kernel mode layer handler, where an unhandled return value can lead to 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 Linux contains a vulnerability in the kernel mode layer handler where an unhandled return value can lead to a null-pointer dereference, causing a kernel panic or system crash resulting in denial of service.

MitigationApply the NVIDIA driver update/patch provided by NVIDIA to address the unhandled return value in the kernel mode layer handler.

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

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. Verify NVIDIA kernel module is loaded
    Run 'lsmod | grep nvidia' to check if the nvidia kernel module is currently loaded in memory
    Affected if The module is loaded (indicating the driver is active)
  2. Retrieve the installed NVIDIA driver version
    Run 'cat /proc/driver/nvidia/version' to read the kernel module version string
    Affected if A version number is returned (driver is installed)
  3. Confirm the product type
    Run 'nvidia-smi' and examine the output, or check if this is a Virtual GPU or Cloud Gaming host by reviewing the system documentation or driver package name
    Affected if The system runs Nvidia Virtual GPU or Nvidia Cloud Gaming software
  4. Compare version against Virtual GPU affected ranges
    If using Virtual GPU, compare your driver version (e.g., from nvidia-smi or /proc/driver/nvidia/version) against: < 11.11, >= 12.0 and < 13.6, or >= 14.0 and < 14.4
    Affected if The installed version falls into any of these ranges
  5. Compare version against Cloud Gaming affected ranges
    If using Cloud Gaming, compare your driver version against: < 525.60.11 or < 525.60.12
    Affected if The installed version is lower than 525.60.11 (or 525.60.12 if that specific version is present)

You are affected if the NVIDIA driver is loaded on a Linux system running Nvidia Virtual GPU or Nvidia Cloud Gaming, and the installed version matches the specific vulnerable ranges listed for either product.

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 provided by NVIDIA to address the unhandled return value in the kernel mode layer handler.

Recommended fix High confidence

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

  1. 1. Identify the current NVIDIA GPU driver version by running `nvidia-smi` or checking the installed package version
  2. 2. Determine which product category applies (Virtual GPU or Cloud Gaming)
  3. 3. For Virtual GPU users: upgrade to version 11.11 or later (if on 12.x branch, upgrade to 13.6+; if on 14.x branch, upgrade to 14.4+)
  4. 4. For Cloud Gaming users: upgrade to version 525.60.12 or later
  5. 5. Download the appropriate driver from NVIDIA's official website or package repository
  6. 6. Stop any running GPU applications or services
  7. 7. Install the new driver package using the standard installation method (e.g., apt-get, yum, or run file)
  8. 8. Reboot the system to load the updated kernel module
Caveat Standard driver update - review NVIDIA release notes for any behavior changes; ensure guest OS virtual GPU configurations are compatible with new version

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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