dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-42259

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
57/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 (nvidia.ko), where an integer overflow may lead to 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

The NVIDIA GPU Display Driver for Linux contains an integer overflow vulnerability in the kernel mode layer (nvidia.ko). When certain integer values overflow during processing in this kernel-mode component, it can trigger a denial of service condition, potentially causing system instability or crash.

MitigationApply the NVIDIA GPU driver update/patch provided by NVIDIA to address the integer overflow vulnerability in the kernel-mode driver. Given this is a kernel-level component, patching should be performed with appropriate system backup and maintenance window planning.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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. Locate the NVIDIA kernel module
    Run 'find /lib/modules -name "nvidia*.ko" 2>/dev/null' to find the nvidia.ko kernel module file
    Affected if The nvidia.ko module file is not found (driver not installed)
  2. Get the NVIDIA driver version
    Run 'modinfo nvidia 2>/dev/null | grep version' or check the file version directly using 'modinfo /lib/modules/$(uname -r)/updates/dkms/nvidia.ko 2>/dev/null | grep version'
    Affected if No version information is returned (module not loaded or not installed)
  3. Compare installed version to affected ranges
    Compare the obtained version against these ranges: 390.x before 390.157, 470.x before 470.161.03, 510.x before 510.108.03, 515.x before 515.86.01, 525.x before 525.60.11, 450.x before 450.216.04
    Affected if The installed version falls within any of the affected ranges listed above
  4. Verify kernel module is loaded
    Run 'lsmod | grep nvidia' to check if the nvidia kernel module is currently loaded in memory
    Affected if The module is loaded (vulnerability only applies when the kernel mode component is active)

You are affected if the NVIDIA kernel mode driver (nvidia.ko) is installed and its version falls within any of the 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 GPU driver update/patch provided by NVIDIA to address the integer overflow vulnerability in the kernel-mode driver. Given this is a kernel-level component, patching should be performed with appropriate system backup and maintenance window planning.

Recommended fix High confidence

390.157 (for 390.x branch), 470.161.03 (for 470.x branch), 510.108.03 (for 510.x branch), 515.86.01 (for 515.x branch), or 525.60.12 (for Cloud Gaming)

  1. 1. Identify the currently installed NVIDIA driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. Determine which driver branch (390, 470, 510, 515, or 525 for Cloud Gaming) is currently in use
  3. 3. Download the appropriate fixed driver version for your branch from the NVIDIA website: 390.157, 470.161.03, 510.108.03, 515.86.01, or 525.60.12
  4. 4. Stop the X server or graphical display manager: `sudo systemctl stop gdm3` (or `lightdm`/`sddm` depending on your setup)
  5. 5. Uninstall the existing NVIDIA driver: `sudo apt remove --purge nvidia-*` or use the.run file with `--uninstall`
  6. 6. For Debian 10, ensure non-free repositories are enabled in `/etc/apt/sources.list`
  7. 7. Install the new driver package: `sudo apt install nvidia-driver-390` (or appropriate version for your branch)
  8. 8. Reboot the system: `sudo reboot`
Caveat Driver updates may require kernel module rebuilds; ensure kernel compatibility before upgrading; some older GPU models may not be supported in newer driver branches

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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