Gpu Display DriverApplication · Nvidia

CVE-2022-42254

HIGH · 7.8 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
80/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, 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

NVIDIA GPU Display Driver for Linux contains an out-of-bounds array access vulnerability in the kernel mode layer (nvidia.ko). This memory safety flaw in the kernel-space driver can allow an attacker to access memory outside array bounds, potentially causing denial of service, data tampering, or information disclosure.

MitigationUpdate the NVIDIA GPU Display Driver to the patched version provided by NVIDIA. This is a kernel-level driver vulnerability requiring a driver update and system reboot to apply the fix.

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:>= 470, < 470.161.03>= 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
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 on Linux
    Check if the nvidia.ko kernel module exists or is loaded by running 'lsmod | grep nvidia' or checking /sys/module/nvidia/version
    Affected if The nvidia kernel module is not present, meaning the driver is not installed and this CVE does not apply.
  2. Identify the installed driver version
    Run 'nvidia-smi' to display driver version information, or check the kernel module version via 'modinfo nvidia'
    Affected if Unable to retrieve a driver version, indicating NVIDIA driver may not be properly installed.
  3. Compare version against affected ranges for GPU Display Driver
    Check if the installed version falls within: 470.x (before 470.161.03), 510.x (before 510.108.03), or 515.x (before 515.86.01
    Affected if The installed version is within any of these vulnerable ranges.
  4. Compare version against affected ranges for Virtual GPU or Cloud Gaming
    If using vGPU or Cloud Gaming, check version against: vGPU < 11.11, 12.x-13.x (before 13.6), 14.x-14.4 (before 14.4); Cloud Gaming < 525.60.11 or < 525.60.12
    Affected if The installed virtual GPU or cloud gaming software version is within any of these vulnerable ranges.
  5. Confirm Linux kernel is the target OS
    Verify the operating system is Linux since this CVE specifically affects the Linux kernel mode driver (nvidia.ko)
    Affected if The system is not running Linux, as this vulnerability only affects the Linux kernel-space driver.

The system is affected if the installed NVIDIA driver version (on Linux) matches any of the vulnerable version ranges: 470.x before 470.161.03, 510.x before 510.108.03, 515.x before 515.86.01, vGPU versions before 11.11/13.6/14.4, or Cloud Gaming versions before 525.60.11/525.60.12.

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

Update the NVIDIA GPU Display Driver to the patched version provided by NVIDIA. This is a kernel-level driver vulnerability requiring a driver update and system reboot to apply the fix.

Recommended fix High confidence

GPU Display Driver: 470.161.03 (470 branch), 510.108.03 (510 branch), or 515.86.01 (515 branch); vGPU: 11.11, 13.6, or 14.4 depending on branch; Cloud Gaming: 525.60.11 or later

  1. Identify the currently installed NVIDIA driver version using `nvidia-smi` or checking /proc/driver/nvidia/version
  2. Determine the product type (GPU Display Driver, vGPU, or Cloud Gaming) to select the correct fixed version
  3. For GPU Display Driver: Download the appropriate installer from nvidia.com/drivers (versions 470.161.03, 510.108.03, or 515.86.01 depending on your branch)
  4. For vGPU: Upgrade to version 11.11, 13.6, or 14.4 depending on your branch
  5. For Cloud Gaming: Upgrade to version 525.60.11 or later
  6. Stop the display manager (e.g., `sudo systemctl stop gdm` or `sudo service lightdm stop`) if upgrading the kernel mode driver
  7. Run the NVIDIA driver installer with elevated privileges: `sudo ./NVIDIA-Linux-x86_64-<version>.run`
  8. Reboot the system: `sudo reboot`
Caveat Kernel driver updates may require system reboot; ensure compatibility with CUDA versions and dependent applications 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-42254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-42254 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