dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-42257

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 information disclosure, data tampering 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

Integer overflow vulnerability in the NVIDIA GPU Display Driver for Linux kernel mode layer (nvidia.ko) that could allow an attacker to cause information disclosure, data tampering, or denial of service.

MitigationUpdate the NVIDIA GPU Display Driver for Linux to a version that includes the patch for CVE-2022-42257, following NVIDIA's security bulletin and ensuring kernel 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:>= 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. Check if NVIDIA kernel driver is loaded
    Run lsmod | grep nvidia to list loaded NVIDIA kernel modules
    Affected if If nvidia.ko or nvidia_*.ko modules are loaded, the system has the vulnerable component
  2. Identify installed NVIDIA driver version
    Run cat /proc/driver/nvidia/version or check /sys/module/nvidia/version to read the driver version string
    Affected if The driver version displayed is within any of these ranges: 390.x to 390.156, 470.x to 470.161.02, 510.x to 510.108.02, 515.x to 515.86.00, 525.x to 525.60.10, or 450.x to 450.216.03
  3. Check NVIDIA driver package version on Debian
    For Debian 10 systems, run dpkg -l | grep nvidia to list installed NVIDIA packages and their versions
    Affected if Any nvidia driver package version from Debian 10 matches the affected kernel driver version ranges
  4. Verify NVIDIA Virtual GPU or Cloud Gaming versions if applicable
    Check the installed version of nvidia-vgpu-config or nvidia-cloud-gaming packages via package manager or installed software metadata
    Affected if nvidia-vgpu software is below 11.11, or between 12.0-13.5, or between 14.0-14.3, or cloud gaming is below 525.60.12

The system is affected if the NVIDIA Linux kernel driver (nvidia.ko) version falls within any of the documented 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

Update the NVIDIA GPU Display Driver for Linux to a version that includes the patch for CVE-2022-42257, following NVIDIA's security bulletin and ensuring kernel compatibility.

Recommended fix High confidence

NVIDIA GPU Display Driver: 390.157, 470.161.03, 510.108.03, or 515.86.01 (depending on driver branch); Cloud Gaming: 525.60.12; Virtual GPU: 11.11/13.6/14.4

  1. Identify the currently installed NVIDIA GPU driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. For Gpu Display Driver: Download and install the appropriate fixed version from NVIDIA's official driver download page based on your GPU model and series (390.157, 470.161.03, 510.108.03, or 515.86.01)
  3. For Cloud Gaming: Upgrade to version 525.60.12 or later
  4. For Virtual GPU: Upgrade to version 11.11, 13.6, or 14.4 (or later) depending on your current branch
  5. Reboot the system after installing the driver update
  6. Verify the installed version matches the fixed release using: `nvidia-smi`
Caveat Kernel driver updates may require matching kernel headers; ensure system kernel compatibility before upgrading; some older GPU models may have limited driver options

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