dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34673

HIGH · 7.3 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 515.86.01 or later.
See remediation →
75/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 (nvidia.ko), where an out-of-bounds array access may lead to denial of service, information disclosure, 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 out-of-bounds array access vulnerability in the kernel mode layer (nvidia.ko). This memory safety issue in the kernel-space driver can be triggered to cause denial of service, potentially expose sensitive information, or allow data tampering.

MitigationUpdate the NVIDIA GPU Display Driver for Linux to the patched version provided by NVIDIA. Prioritize updates on systems running untrusted workloads or those exposed to untrusted GPU inputs.

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

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 kernel driver is loaded
    Run 'lsmod | grep nvidia' to check if the nvidia.ko kernel module is currently loaded in memory
    Affected if If nvidia.ko is not loaded, the vulnerability is not currently exploitable in this running state
  2. Identify the installed driver version
    Run 'nvidia-smi' and note the Driver Version field, or check /sys/module/nvidia/version for the kernel module version
    Affected if Driver version must be captured to compare against the vulnerable range
  3. Compare version against vulnerable range
    Verify the installed version is >= 515 AND < 515.86.01. If using the nvidia-smi output, the driver version format is typically 515.xx.xx
    Affected if If version falls within >= 515 and < 515.86.01, the installed driver is affected by this CVE
  4. Confirm Linux-specific kernel module
    Confirm the driver is the Linux kernel module by checking that nvidia.ko exists in the kernel module directory (typically /lib/modules/$(uname -r)/kernel/drivers/video/)
    Affected if This vulnerability only affects the Linux kernel driver (nvidia.ko), not Windows or other OS versions

A system is affected if the NVIDIA Linux display driver module (nvidia.ko) is loaded and its version falls within the range of 515.00.00 through 515.85.xx (inclusive).

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 515.86.01 or later
Fixed in 515.86.01
Interim mitigation

Update the NVIDIA GPU Display Driver for Linux to the patched version provided by NVIDIA. Prioritize updates on systems running untrusted workloads or those exposed to untrusted GPU inputs.

Recommended fix High confidence

515.86.01

  1. Check current NVIDIA driver version using 'nvidia-smi' or 'cat /proc/driver/nvidia/version'
  2. Stop the display manager/X server (e.g., 'systemctl stop gdm' or 'systemctl stop lightdm')
  3. Download the NVIDIA Linux GPU Display Driver version 515.86.01 or later from nvidia.com/drivers
  4. Make the downloaded installer executable: 'chmod +x NVIDIA-Linux-x86_64-*.run'
  5. Run the installer as root: 'sudo ./NVIDIA-Linux-x86_64-*.run'
  6. Reboot the system: 'sudo reboot'
  7. Verify the fix by checking the driver version again
Caveat Driver upgrade may require recompiling against new kernel headers; ensure kernel-devel packages match your running kernel 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
  • 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-34673 — 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-34673 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