dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34684

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 (nvidia.ko), where an off-by-one error may lead to data tampering 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 · high confidence

An off-by-one error in the NVIDIA GPU Display Driver for Linux in the kernel mode layer (nvidia.ko) allows local attackers to potentially tamper with data or disclose information due to improper bounds checking.

MitigationApply the NVIDIA-provided security patch/update for the GPU Display Driver. If a patch is unavailable, restrict local access to systems with GPUs and monitor for suspicious behavior.

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:>= 510, < 510.108.03>= 515, < 515.86.01
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
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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. Confirm NVIDIA kernel module is loaded
    Run 'lsmod | grep nvidia' to list loaded NVIDIA kernel modules, or check 'ls -la /proc/driver/' for nvidia directory existence
    Affected if The nvidia.ko module is present and loaded in memory
  2. Identify the installed driver version
    Run 'cat /proc/driver/nvidia/version' or 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' to retrieve the installed driver version number
    Affected if The command returns a version number that falls within or overlaps the affected ranges
  3. Compare version against affected ranges for Linux Display Driver
    Compare your installed version against: 510.x series < 510.108.03, or 515.x series < 515.86.01. Versions 510.108.03 and above, or 515.86.01 and above are NOT affected
    Affected if Your version is 510.108.02 or lower, OR 515.86.00 or lower
  4. Compare version against affected ranges for vGPU or Cloud Gaming if applicable
    If using Virtual GPU or Cloud Gaming, compare against: vGPU < 11.11, 12.0-13.5.x, 14.0-14.3.x; Cloud Gaming < 525.60.11 or < 525.60.12
    Affected if Your vGPU or Cloud Gaming version is lower than the safe versions listed

You are affected if the NVIDIA Linux display driver (nvidia.ko) is loaded and its version is within 510.x < 510.108.03 or 515.x < 515.86.01, or if using affected vGPU/Cloud Gaming versions.

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-provided security patch/update for the GPU Display Driver. If a patch is unavailable, restrict local access to systems with GPUs and monitor for suspicious behavior.

Recommended fix High confidence

Gpu Display Driver: 510.108.03+ or 515.86.01+ | Virtual Gpu: 11.11+, 13.6+, or 14.4+ | Cloud Gaming: 525.60.12+

  1. 1. Identify the installed NVIDIA driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. For Gpu Display Driver on Linux: If running version 510.x, upgrade to 510.108.03 or later. If running version 515.x, upgrade to 515.86.01 or later
  3. 3. For Virtual Gpu: If running version < 11.11, upgrade to 11.11 or later. If running 12.0-13.5.x, upgrade to 13.6 or later. If running 14.0-14.3.x, upgrade to 14.4 or later
  4. 4. For Cloud Gaming: Upgrade to 525.60.12 or later
  5. 5. Download the appropriate driver from the official NVIDIA website or use your distribution's package manager
  6. 6. Stop any applications using the GPU, then stop the display manager (e.g., `systemctl stop gdm` or `systemctl stop lightdm`)
  7. 7. Install the new driver package (e.g., `apt-get install nvidia-driver-510` or use therun file)
  8. 8. Reboot the system to load the new kernel module
Caveat Review NVIDIA's driver release notes for any API changes or deprecated features before upgrading; ensure guest OS and hypervisor versions are compatible with the new virtual GPU driver versions

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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