dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-31608

HIGH · 7.8 CVSS v3.1 Published 2022-11-19
Fix available
A fix is available. Upgrade to 390.154 / 450.203.03 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 an optional D-Bus configuration file, where a local user with basic capabilities can impact protected D-Bus endpoints, which may lead to code execution, denial of service, escalation of privileges, information disclosure, and 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

A detailed technical summary for this CVE is being prepared.

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.154>= 470, < 470.141.03>= 510, < 510.85.02>= 515, < 515.65.01>= 450, < 450.203.03

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

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 390.154 / 450.203.03 / 470.141.03 or later
Fixed in 390.154450.203.03470.141.03
Vendor patch nvidia.custhelp.com →
Recommended fix High confidence

Upgrade to 390.154 (for 390.x branch), 470.141.03 (for 470.x branch), 510.85.02 (for 510.x branch), or 515.65.01 (for 515.x branch)

  1. 1. Identify current NVIDIA driver version by running: nvidia-smi or cat /proc/driver/nvidia/version
  2. 2. Determine which version branch (390, 470, 510, or 515) is currently installed
  3. 3. Download the appropriate fixed driver version from NVIDIA's official website or package repository matching your branch
  4. 4. For branch 390.x: upgrade to version 390.154 or later
  5. 5. For branch 470.x: upgrade to version 470.141.03 or later
  6. 6. For branch 510.x: upgrade to version 510.85.02 or later
  7. 7. For branch 515.x: upgrade to version 515.65.01 or later
  8. 8. Reboot the system after driver installation to load the updated driver
Caveat Standard NVIDIA driver upgrade risks apply - ensure compatibility with your kernel version and confirm any CUDA/ML framework version requirements

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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