dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34680

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 integer truncation can lead to an out-of-bounds read, 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

The NVIDIA GPU Display Driver for Linux contains an integer truncation vulnerability in its kernel mode layer handler. This flaw allows an attacker to trigger an out-of-bounds read condition, potentially causing a denial of service through system instability or crash.

MitigationApply the latest NVIDIA GPU driver update for Linux that addresses this vulnerability. Until patched, monitor for suspicious GPU driver interactions that could exploit this integer truncation flaw.

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
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 'lsmod | grep nvidia' to check if the nvidia kernel module is loaded, or check for /proc/driver/nvidia/version
    Affected if No NVIDIA driver kernel module is loaded means the system is not affected by this specific driver vulnerability
  2. Retrieve the installed driver version
    Execute 'cat /proc/driver/nvidia/version' or run 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' to obtain the installed driver version number
    Affected if The command fails or returns no version indicates no NVIDIA driver is installed
  3. Compare version against affected ranges
    Compare the installed version number to these 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
    Affected if The installed version falls within any of these ranges means the system is vulnerable
  4. Check if kernel mode setting is active
    Verify the nvidia kernel module is actively handling graphics by checking 'ls -la /dev/nvidia*' to confirm driver device nodes exist
    Affected if The driver is loaded and active (devices exist under /dev/nvidia), combined with a vulnerable version from step 3, confirms the exposure

A system is affected if it runs any NVIDIA GPU Display Driver for Linux version within the vulnerable ranges listed, with the kernel module 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 latest NVIDIA GPU driver update for Linux that addresses this vulnerability. Until patched, monitor for suspicious GPU driver interactions that could exploit this integer truncation flaw.

Recommended fix High confidence

NVIDIA GPU Display Driver: 390.157 / 470.161.03 / 510.108.03 / 515.86.01; Cloud Gaming: 525.60.12+; Virtual GPU: 11.11 / 13.6 / 14.4+

  1. 1. Identify the current NVIDIA driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. Determine which product category applies (GPU Display Driver, Cloud Gaming, or Virtual GPU)
  3. 3. Download the appropriate fixed driver version from the NVIDIA website (nvidia.com) or your distribution's package manager
  4. 4. For Linux GPU Display Driver: Upgrade to version 390.157, 470.161.03, 510.108.03, or 515.86.01 depending on your current branch
  5. 5. For Cloud Gaming: Upgrade to version 525.60.12 or later
  6. 6. For Virtual GPU: Upgrade to version 11.11, 13.6, or 14.4 depending on your current branch
  7. 7. Reboot the system after installing the driver update
Caveat Driver upgrades may require kernel version compatibility checks; ensure the new driver supports your Linux kernel version 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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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