dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-42263

HIGH · 7.1 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
73/100
Remediation priority · Elevated
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 handler, where an Integer overflow may lead to denial of service 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 integer overflow vulnerability in the kernel mode layer (nvidia.ko). The overflow occurs in a handler function within the kernel-mode component, which runs with elevated privileges. Successful exploitation may lead to denial of service (system crash/hang) or information disclosure (potential kernel memory read).

MitigationApply the NVIDIA driver security update or patch. Prior to deployment in production, test GPU workload functionality to ensure driver compatibility.

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
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check if NVIDIA driver kernel module is loaded
    Run 'lsmod | grep nvidia' to list loaded NVIDIA kernel modules
    Affected if Module 'nvidia' or 'nvidia_uvm' appears in the output, indicating the driver is active
  2. Identify installed NVIDIA driver version
    Run 'cat /proc/driver/nvidia/version' or use 'nvidia-smi --query-gpu=driver_version --format=csv,noheader'
    Affected if Version output is obtained, confirming NVIDIA driver is installed
  3. Compare driver version against affected ranges
    Compare the version from step 2 against: 470.x before 470.161.03; 510.x before 510.108.03; 515.x before 515.86.01; 450.x before 450.216.04
    Affected if Installed version falls within any of these vulnerable ranges
  4. Check NVIDIA vGPU software version if applicable
    For virtual environments, check vGPU software version via 'nvidia-smi' or hypervisor documentation
    Affected if vGPU version is < 11.11, or >= 12.0 and < 13.6, or >= 14.0 and < 14.4
  5. Verify kernel module file version
    Examine the nvidia.ko file directly: 'modinfo nvidia 2>/dev/null | grep version' or check /sys/module/nvidia/version
    Affected if Version matches vulnerable ranges from step 3

Environment is affected if NVIDIA GPU driver for Linux is installed and the driver version falls within any of the vulnerable version ranges (450.x < 450.216.04, 470.x < 470.161.03, 510.x < 510.108.03, 515.x < 515.86.01), or for virtual/gaming deployments their respective vulnerable 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 driver security update or patch. Prior to deployment in production, test GPU workload functionality to ensure driver compatibility.

Recommended fix High confidence

Upgrade to the minimum fixed version for your product branch: 470.161.03, 510.108.03, 515.86.01, or 450.216.04 for GPU Display Driver; 11.11, 13.6, or 14.4 for Virtual GPU; 525.60.11 or 525.60.12 for Cloud Gaming

  1. 1. Identify the currently installed NVIDIA driver version using 'nvidia-smi' or checking /proc/driver/nvidia/version
  2. 2. Determine which product category applies (GPU Display Driver, Virtual GPU, or Cloud Gaming)
  3. 3. Download the appropriate fixed version from NVIDIA's official website or package repository
  4. 4. For GPU Display Driver: Upgrade to 470.161.03+ (for 470.x branch), 510.108.03+ (for 510.x branch), 515.86.01+ (for 515.x branch), or 450.216.04+ (for 450.x branch)
  5. 5. For Virtual GPU: Upgrade to 11.11+, 13.6+, or 14.4+ depending on your current branch
  6. 6. For Cloud Gaming: Upgrade to 525.60.11+ or 525.60.12+
  7. 7. Reboot the system after installation to load the new kernel module
  8. 8. Verify the installed version matches or exceeds the fixed version using 'nvidia-smi'
Caveat Major driver upgrades may require kernel rebuilds or compatibility checks with existing CUDA/ML workloads; test in staging before production deployment

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-42263 — 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-42263 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