dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-42264

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, where an unprivileged regular user can cause the use of an out-of-range pointer offset, which may lead to data tampering, data loss, information disclosure, or denial of service.

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 a kernel mode layer vulnerability where an unprivileged regular user can cause the use of an out-of-range pointer offset, potentially leading to data tampering, loss, information disclosure, or denial of service.

MitigationApply the NVIDIA GPU driver patch/update to the latest version. For immediate workarounds, restrict access to GPU device nodes (/dev/nvidia*) to privileged users only until the patch can be deployed.

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>= 450, < 450.216.04
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. Identify NVIDIA driver installation
    Run 'ls -la /dev/nvidia*' to list NVIDIA device nodes, or run 'nvidia-smi --query-gpu=driver_version --format=csv,noheader' to query the driver version
    Affected if No NVIDIA device nodes exist or nvidia-smi fails, indicating no NVIDIA driver is installed
  2. Determine installed driver version for Linux display driver
    Check the kernel module version with 'cat /proc/driver/nvidia/version' or use 'nvidia-smi' to display driver version information
    Affected if The displayed version falls within any of these ranges: >=470 and <470.161.03; >=510 and <510.108.03; >=515 and <515.86.01; >=450 and <450.216.04
  3. Determine installed Virtual GPU or Cloud Gaming version
    Check the installed NVIDIA vGPU Manager or Cloud Gaming package version using your package manager (dpkg -l or rpm -qa) or check the software version via its management interface
    Affected if The version is <11.11, or >=12.0 and <13.6, or >=14.0 and <14.4 for vGPU; or <525.60.11 or <525.60.12 for Cloud Gaming
  4. Verify user access to GPU device nodes
    Run 'ls -l /dev/nvidia*' to inspect permissions on NVIDIA device files and check group ownership
    Affected if Device nodes are readable or writable by non-root users without special privileges (check group permissions and world permissions)

You are affected if an unprivileged user can access /dev/nvidia* devices AND your installed NVIDIA driver, vGPU, or Cloud Gaming version matches one of the vulnerable version ranges listed.

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 GPU driver patch/update to the latest version. For immediate workarounds, restrict access to GPU device nodes (/dev/nvidia*) to privileged users only until the patch can be deployed.

Recommended fix High confidence

Gpu Display Driver: 470.161.03, 510.108.03, 515.86.01, or 450.216.04 (depending on branch); Virtual Gpu: 11.11, 13.6, or 14.4; Cloud Gaming: 525.60.11 or later

  1. Identify the current NVIDIA driver version by running `nvidia-smi` or checking `/proc/driver/nvidia/version`
  2. Determine which product line applies to your system: Gpu Display Driver, Virtual Gpu, or Cloud Gaming
  3. For Gpu Display Driver: Download and install the appropriate fixed version for your driver branch (470.161.03 for 470.x, 510.108.03 for 510.x, 515.86.01 for 515.x, or 450.216.04 for 450.x)
  4. For Virtual Gpu: Upgrade to version 11.11, 13.6, or 14.4 (or later) depending on your current branch
  5. For Cloud Gaming: Upgrade to version 525.60.11 or later
  6. Reboot the system after installing the new driver to load the updated kernel module
  7. Verify the fix by confirming the new driver version with `nvidia-smi`
Caveat Review NVIDIA driver release notes for potential compatibility changes with specific GPU models or CUDA versions 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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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