dbcve.org
Gpu Display DriverApplication · Nvidia

CVE-2022-34674

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-30
Fix available
A fix is available. Upgrade to 11.11 / 13.6 or later.
See remediation →
63/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 a helper function maps more physical pages than were requested, which may lead to undefined behavior or an information leak.

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 a vulnerability in the kernel mode layer where a helper function incorrectly maps more physical pages than were requested by the caller. This memory mapping discrepancy can lead to undefined behavior or an information leak due to the unintended exposure of additional memory pages.

MitigationApply the NVIDIA GPU driver update or patch that addresses this kernel mode layer page mapping vulnerability. Verify the fix does not introduce regressions in display functionality or memory management.

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
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

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 installed NVIDIA driver version
    Run 'nvidia-smi' or check the installed package version with 'dpkg -l | grep nvidia' or 'rpm -qa | grep nvidia'
    Affected if The driver version falls within any of these vulnerable ranges: 390.x (< 390.157), 470.x (< 470.161.03), 510.x (< 510.108.03), 515.x (< 515.86.01), 525.x (< 525.60.11), or 450.x (< 450.216.04)
  2. Verify NVIDIA kernel module is loaded
    Run 'lsmod | grep nvidia' to confirm the kernel mode driver is currently loaded in memory
    Affected if The nvidia kernel module is loaded and its version matches any of the vulnerable versions listed above
  3. Check kernel module file version
    Run 'modinfo nvidia' and look for the 'version' or 'srcversion' field, or check the driver file directly in /lib/modules/$(uname -r)/video/
    Affected if The module version string matches a vulnerable release version
  4. Confirm operating system is Debian 10
    Run 'cat /etc/os-release' or 'lsb_release -a' to identify the OS version
    Affected if Running Debian 10.0 with an affected NVIDIA driver version installed
  5. Check for NVIDIA Virtual GPU software
    If running in a virtualized environment, check for 'nvidia-vgpu-mgr' service with 'systemctl status nvidia-vgpu-mgr' or ps aux | grep vgpu
    Affected if Using Nvidia Virtual GPU software with version < 11.11, or >= 12.0 and < 13.6, or >= 14.0 and < 14.4

You are affected if the NVIDIA GPU driver or virtual GPU software version running in your Linux environment falls within any of the vulnerable version ranges listed in the CVE and the kernel mode driver is actively loaded.

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 or patch that addresses this kernel mode layer page mapping vulnerability. Verify the fix does not introduce regressions in display functionality or memory management.

Recommended fix High confidence

Gpu Display Driver: 390.157, 470.161.03, 510.108.03, or 515.86.01 | Cloud Gaming: 525.60.12 or 525.60.11 | Virtual GPU: 11.11, 13.6, or 14.4

  1. 1. Identify the installed NVIDIA driver version using: `nvidia-smi` or `cat /proc/driver/nvidia/version`
  2. 2. For Gpu Display Driver: Download and install the appropriate fixed version from NVIDIA's official driver download page (https://www.nvidia.com/Download/index.aspx) based on your GPU model
  3. 3. For Debian 10.0: Run `apt-get update && apt-get install nvidia-driver` to get the patched version from Debian repositories
  4. 4. For Cloud Gaming: Update to version 525.60.12 or 525.60.11 from NVIDIA's GeForce Experience or driver download page
  5. 5. For Virtual GPU: Update to version 11.11, 13.6, or 14.4 from NVIDIA's vGPU software downloads
  6. 6. Reboot the system after driver installation to load the new kernel module
  7. 7. Verify the fix by checking the driver version matches or exceeds the fixed versions listed
Caveat Major version upgrades (e.g., 390 to 470, 470 to 510) may require CUDA toolkit version updates and could introduce compatibility changes with older GPU models

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

Fix this in Gpu Display Driver Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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