dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34670

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 Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure.

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 where unprivileged users can trigger truncation errors through improper type casting from larger to smaller primitive types, causing data loss that may lead to denial of service or information disclosure.

MitigationApply the latest NVIDIA GPU driver updates for Linux that address this kernel mode layer vulnerability; until patched, monitor for suspicious user activity involving GPU operations.

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
Debian LinuxOperating system
Affected:= 10.0
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
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. Check if NVIDIA driver is installed
    Run 'nvidia-smi' or check for nvidia kernel module with 'lsmod | grep nvidia'
    Affected if nvidia-smi fails or nvidia kernel module is not present means not affected by this specific vulnerability
  2. Get the installed NVIDIA driver version
    Run 'nvidia-smi' and note the Driver Version field, or check '/proc/driver/nvidia/version'
    Affected if Unable to determine version means cannot assess vulnerability status
  3. Compare installed version against affected ranges
    For the main GPU Display Driver: version is vulnerable if it falls in these ranges: 390.x up to 390.157; 470.x up to 470.161.03; 510.x up to 510.108.03; 515.x up to 515.86.01; 525.x up to 525.60.11; 450.x up to 450.216.04
    Affected if Installed version is within any of these ranges indicates affected
  4. Check if kernel mode driver is loaded
    Run 'lsmod | grep nvidia' and verify nvidia.ko or nvidia_uvm.ko modules are loaded
    Affected if Kernel module is loaded and version is vulnerable indicates active exposure to this kernel mode layer flaw

User is affected if they have an NVIDIA GPU Display Driver for Linux installed with a version within the listed vulnerable ranges and the nvidia kernel module is 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 latest NVIDIA GPU driver updates for Linux that address this kernel mode layer vulnerability; until patched, monitor for suspicious user activity involving GPU operations.

Recommended fix High confidence

Upgrade to: 390.157 (if on 390.x branch), 470.161.03 (if on 470.x branch), 510.108.03 (if on 510.x branch), or 515.86.01 (if on 515.x branch). For Virtual GPU: upgrade to 11.11, 13.6, or 14.4 respectively. For Cloud Gaming: upgrade to 525.60.11 or 525.60.12.

  1. Identify current NVIDIA driver version using 'nvidia-smi' or 'cat /proc/driver/nvidia/version'
  2. Determine which driver branch (390.x, 470.x, 510.x, or 515.x) is currently installed
  3. Download the appropriate fixed driver version from NVIDIA's official website or your distribution's package repository
  4. For Debian 10.0: Run 'apt update && apt install nvidia-driver' to get the patched version
  5. For RHEL/CentOS: Run 'yum update nvidia-driver' or 'dnf update nvidia-driver'
  6. For SUSE: Run 'zypper update nvidia-driver'
  7. Reboot the system after driver update to load the new kernel module
  8. Verify the installed version matches the fixed release using 'nvidia-smi'
Caveat Driver updates may require kernel compatibility checks; ensure the kernel version is supported by the new driver. Test in staging environment before production deployment.

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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