dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34675

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 390.157 / 450.216.04 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 Display Driver for Linux contains a vulnerability in the Virtual GPU Manager, where it does not check the return value from 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 Display Driver for Linux contains a vulnerability in the Virtual GPU Manager component where the code fails to validate a pointer before dereferencing it. When a null pointer is encountered without proper error checking, the driver can trigger a kernel panic or crash, resulting in denial of service for virtual GPU instances.

MitigationApply the NVIDIA display driver update or patch that addresses this null-pointer dereference vulnerability. In virtualized environments, ensure VGPU configurations are tested after updates to confirm stability.

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
Gpu Display DriverApplication
Affected:>= 390, < 390.157>= 470, < 470.161.03>= 510, < 510.108.03>= 515, < 515.86.01>= 525, < 525.60.11>= 450, < 450.216.04
Cloud GamingApplication
Affected:< 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 driver is installed
    Run `nvidia-smi` or check `cat /proc/driver/nvidia/version` to confirm the NVIDIA display driver is present on the system
    Affected if nvidia-smi fails or the version file does not exist, indicating no NVIDIA driver is installed and this CVE does not apply
  2. Identify the installed driver version
    Run `nvidia-smi` and note the Driver Version field, or read from `/proc/driver/nvidia/version`
    Affected if The driver version cannot be determined - you cannot assess vulnerability without a version number
  3. Check if Virtual GPU Manager is in use
    Run `lsmod | grep -i vgpu` or check for the nvidia-vgpu-mgr process via `ps aux | grep vgpu` to determine if the Virtual GPU Manager component is loaded or active
    Affected if Virtual GPU Manager is not loaded or used - the vulnerability only affects systems with vGPU functionality enabled
  4. Compare version against affected ranges
    Compare your installed driver version to the following vulnerable ranges: 390.x before 390.157; 470.x before 470.161.03; 510.x before 510.108.03; 515.x before 515.86.01; 525.x before 525.60.11; 450.x before 450.216.04. Also check Nvidia Cloud Gaming versions below 525.60.12
    Affected if Your driver version falls within any of the listed ranges AND Virtual GPU Manager is enabled - you are affected by this null-pointer dereference vulnerability that can cause kernel panic

You are affected if you have an NVIDIA display driver for Linux with Virtual GPU Manager enabled and your driver version is within any of these ranges: 390.x < 390.157, 470.x < 470.161.03, 510.x < 510.108.03, 515.x < 515.86.01, 525.x < 525.60.11, or 450.x < 450.216.04 (or Nvidia Cloud Gaming < 525.60.12).

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 390.157 / 450.216.04 / 470.161.03 or later
Fixed in 390.157450.216.04470.161.03
Interim mitigation

Apply the NVIDIA display driver update or patch that addresses this null-pointer dereference vulnerability. In virtualized environments, ensure VGPU configurations are tested after updates to confirm stability.

Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 390.157, 470.161.03, 510.108.03, 515.86.01, or 525.60.12 (Cloud Gaming)

  1. 1. Identify the currently installed NVIDIA driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. Determine which driver branch you are currently using (390, 470, 510, 515, or Cloud Gaming)
  3. 3. Download the appropriate fixed driver version from NVIDIA's official website or your Linux distribution's repository:
  4. - For 390.x branch: Upgrade to version 390.157 or later
  5. - For 470.x branch: Upgrade to version 470.161.03 or later
  6. - For 510.x branch: Upgrade to version 510.108.03 or later
  7. - For 515.x branch: Upgrade to version 515.86.01 or later
  8. - For Cloud Gaming: Upgrade to version 525.60.12 or later
Caveat Standard upgrade risk - ensure compatibility with your GPU hardware and verify guest VM virtual GPU configuration works after upgrade

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

Fix this in Gpu Display Driver 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-34675 — 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-34675 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