dbcve.org
Virtual GpuApplication · Nvidia

CVE-2022-42255

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, 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 · high confidence

This is an out-of-bounds array access vulnerability in the NVIDIA GPU Display Driver's kernel mode layer (nvidia.ko) for Linux. The flaw allows a local attacker to potentially cause denial of service, expose sensitive information from kernel memory, or corrupt data through improper array indexing in the driver.

MitigationApply the NVIDIA security update containing the fix for this vulnerability. Until patched, monitor for unauthorized local access to systems with NVIDIA GPU drivers installed.

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
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 kernel driver is installed
    Run 'lsmod | grep nvidia' to check if the nvidia kernel module is loaded, or 'ls /lib/modules/$(uname -r)/kernel/drivers/video/nvidia*' to check for driver files
    Affected if The nvidia.ko kernel module is present on the system
  2. Obtain the installed driver version
    Run 'nvidia-smi' to display driver version information, or check '/proc/driver/nvidia/version' for the kernel module version
    Affected if Driver version is returned by these commands
  3. Compare version against affected Virtual GPU ranges
    Compare your Virtual GPU driver version to: < 11.11, >= 12.0 and < 13.6, >= 14.0 and < 14.4
    Affected if Installed version falls within any of these ranges: less than 11.11, 12.0-13.5.x, or 14.0-14.3.x
  4. Compare version against affected Cloud Gaming ranges
    Compare your Cloud Gaming driver version to: < 525.60.11 or < 525.60.12
    Affected if Installed version is any version prior to 525.60.11, or prior to 525.60.12 if using a 525.xx release

A system is affected if the NVIDIA Linux kernel driver (nvidia.ko) is installed and its version matches any of the affected Virtual GPU or Cloud Gaming version ranges.

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 update containing the fix for this vulnerability. Until patched, monitor for unauthorized local access to systems with NVIDIA GPU drivers installed.

Recommended fix High confidence

Virtual GPU: 11.11, 13.6, or 14.4 (or later) | Cloud Gaming: 525.60.11 or 525.60.12 (or later)

  1. 1. Identify the current NVIDIA GPU driver version by running: nvidia-smi or checking /proc/driver/nvidia/version
  2. 2. Determine which product category applies (Virtual GPU or Cloud Gaming)
  3. 3. For Virtual GPU users: Upgrade to version 11.11 or later, 13.6 or later, or 14.4 or later
  4. 4. For Cloud Gaming users: Upgrade to version 525.60.11 or later, or 525.60.12 or later
  5. 5. Download the appropriate driver from NVIDIA's official website or package repository
  6. 6. Install the driver following NVIDIA's standard installation procedure for Linux
  7. 7. Reboot the system to load the new kernel module
  8. 8. Verify the new driver version is installed using nvidia-smi

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

Fix this in Virtual Gpu Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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