dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-42258

HIGH · 7.3 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 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 integer overflow may lead to denial of service, 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 · moderate confidence

This is an integer overflow vulnerability in the NVIDIA GPU kernel mode driver (nvidia.ko) for Linux. The integer overflow in the kernel mode layer can cause the driver to misbehave, potentially leading to denial of service (system crash), data tampering (memory corruption), or information disclosure (reading unintended memory contents).

MitigationApply the NVIDIA security patch by updating to the fixed version of the NVIDIA GPU Display Driver for Linux. This is a kernel-level driver issue, so the fix must come from NVIDIA's official driver update.

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
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 kernel module is currently loaded in memory
    Affected if The nvidia module is loaded - if it is not loaded, the vulnerability cannot be exploited in the current session
  2. Identify installed NVIDIA driver version
    Run 'cat /sys/module/nvidia/version' or 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' to retrieve the installed driver version number
    Affected if The displayed version falls within any of these ranges: 390.x (before 390.157), 450.x (before 450.216.04), 470.x (before 470.161.03), 510.x (before 510.108.03), 515.x (before 515.86.01), or 525.x (before 525.60.11)
  3. Check Debian distribution version if applicable
    If running Debian 10, run 'cat /etc/debian_version' to confirm the Debian release version
    Affected if The system is Debian 10.0 and has an NVIDIA driver installed - the driver version check above takes precedence for determining actual vulnerability status

You are affected if the NVIDIA kernel driver is loaded and its version falls within any of the vulnerable version ranges listed (390.x through 525.x depending on branch), regardless of whether the system is Debian 10 or another Linux distribution.

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 security patch by updating to the fixed version of the NVIDIA GPU Display Driver for Linux. This is a kernel-level driver issue, so the fix must come from NVIDIA's official driver update.

Recommended fix High confidence

GPU Display Driver: 390.157, 470.161.03, 510.108.03, or 515.86.01 | Cloud Gaming: 525.60.12 | Virtual GPU: 11.11, 13.6, or 14.4

  1. 1. Identify the currently installed NVIDIA driver version by running 'nvidia-smi' or checking the installed package (e.g., 'dpkg -l | grep nvidia' or 'rpm -qa | grep nvidia')
  2. 2. Determine which NVIDIA product line is affected: GPU Display Driver, Cloud Gaming, or Virtual GPU
  3. 3. For GPU Display Driver: Upgrade to version 390.157 (if using 390.x series), 470.161.03 (if using 470.x series), 510.108.03 (if using 510.x series), or 515.86.01 (if using 515.x series)
  4. 4. For Cloud Gaming: Upgrade to version 525.60.12 or later
  5. 5. For Virtual GPU: Upgrade to version 11.11 (if using 11.x), 13.6 (if using 12.x-13.x), or 14.4 (if using 14.x)
  6. 6. Download the appropriate driver from the official NVIDIA website or use the distribution's package manager to install the updated package
  7. 7. Reboot the system after installation to load the new kernel module
  8. 8. Verify the fix by running 'nvidia-smi' to confirm the new version is loaded
Caveat Check NVIDIA's release notes for compatibility requirements with your CUDA version and Linux 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
  • 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-42258 — 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-42258 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