dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34677

HIGH · 7.1 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
73/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 unprivileged regular user can cause an integer to be truncated, which may lead to denial of service or data tampering.

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 an integer truncation vulnerability in the kernel mode layer handler. An unprivileged regular user can trigger this flaw, potentially causing denial of service or data tampering.

MitigationApply the NVIDIA driver update/patch for CVE-2022-34677. This typically involves updating the NVIDIA GPU Display Driver to a patched version via the appropriate package manager or NVIDIA's driver download page.

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
Cloud GamingApplication
Affected:< 525.60.12< 525.60.11
Virtual GpuApplication
Affected:< 11.11>= 12.0, < 13.6>= 14.0, < 14.4

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 loaded
    Run 'lsmod | grep nvidia' or 'nvidia-smi' to see if the NVIDIA kernel module is active
    Affected if The nvidia kernel module is loaded - the driver is active in the environment
  2. Identify the installed NVIDIA driver version on Linux
    Run 'cat /proc/driver/nvidia/version' or 'nvidia-smi' to obtain the driver version number
    Affected if The displayed version falls within any of these ranges: 390.x to 390.156.x, 470.x to 470.161.02, 510.x to 510.108.02, 515.x to 515.86.00, 525.x to 525.60.10, or 450.x to 450.216.03
  3. Check Debian package version if installed via apt
    Run 'dpkg -l | grep -i nvidia' to list installed NVIDIA packages and their versions
    Affected if Any nvidia-driver package version is below 390.157, 470.161.03, 510.108.03, 515.86.01, or 525.60.11 respectively for the 390, 470, 510, 515, or 525 branch
  4. Verify NVIDIA Virtual GPU software version (if applicable)
    Check the installed nvidia-vgpu软件 version via 'nvidia-smi -q' or the virtual machine hypervisor documentation if running nvidia vGPU
    Affected if The vGPU software version is < 11.11, between 12.0-13.5.x, or between 14.0-14.3.x

You are affected if the NVIDIA GPU driver or vGPU software version is within the vulnerable ranges listed and the kernel mode driver is loaded or installed on the system.

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 for CVE-2022-34677. This typically involves updating the NVIDIA GPU Display Driver to a patched version via the appropriate package manager or NVIDIA's driver download page.

Recommended fix High confidence

Upgrade to the latest NVIDIA GPU driver version within your current branch series: 390.157+, 470.161.03+, 510.108.03+, 515.86.01+, 525.60.12+, or Virtual GPU 11.11+/13.6+/14.4+

  1. 1. Identify the currently installed NVIDIA GPU driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. Based on the installed version branch, download the corresponding fixed driver from NVIDIA's official download page (https://www.nvidia.com/Download/index.aspx) or your distribution's package repository
  3. 3. For Gpu Display Driver >= 390 series: upgrade to version 390.157 or later
  4. 4. For Gpu Display Driver >= 470 series: upgrade to version 470.161.03 or later
  5. 5. For Gpu Display Driver >= 510 series: upgrade to version 510.108.03 or later
  6. 6. For Gpu Display Driver >= 515 series: upgrade to version 515.86.01 or later
  7. 7. For Cloud Gaming: upgrade to version 525.60.12 or later (or 525.60.11 for older branch)
  8. 8. For Virtual GPU: upgrade to 11.11, 13.6, or 14.4 or later depending on your branch
Caveat Driver upgrades may require kernel module recompilation; ensure kernel compatibility and back up configuration before upgrading

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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