Gpu Display DriverApplication · Nvidia

CVE-2022-42260

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

NVD · unedited

NVIDIA vGPU Display Driver for Linux guest contains a vulnerability in a D-Bus configuration file, where an unauthorized user in the guest VM can impact protected D-Bus endpoints, which may lead to code execution, denial of service, escalation of privileges, information disclosure, or data tampering.

Technical summary

dbcve analysis · high confidence

NVIDIA vGPU Display Driver for Linux guest contains a vulnerability in a D-Bus configuration file. An unauthorized user in the guest VM can access protected D-Bus endpoints that should be restricted, potentially leading to code execution, denial of service, privilege escalation, information disclosure, or data tampering.

MitigationUpdate NVIDIA vGPU Display Driver to the latest version containing the patched D-Bus configuration that properly restricts access to protected endpoints. Verify that unauthorized users in guest VMs can no longer access protected D-Bus services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Gpu Display DriverApplication

Affected:>= 470, < 470.161.03>= 510, < 510.108.03>= 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

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify NVIDIA vGPU driver installation

Run 'nvidia-smi' or check for NVIDIA kernel modules with 'lsmod | grep nvidia' in the guest VM

Affected if No NVIDIA driver is present - not vulnerable to this specific CVE which targets the NVIDIA vGPU guest driver
Determine installed driver version

Run 'nvidia-smi' and look at the Driver Version field, or check '/sys/module/nvidia/version'

Affected if Driver version falls within affected ranges: GPU Display Driver 450.x before 450.216.04, 470.x before 470.161.03, or 510.x before 510.108.03; Virtual GPU versions before 11.11, 12.x-13.x before 13.6, 14.x before 14.4; Cloud Gaming before 525.60.11 or 525.60.12
Confirm execution environment is a guest VM

Check if running as a virtual machine using 'systemd-detect-virt' or check for hypervisor indicators in dmesg (hyperv, vmware, kvm, qemu)

Affected if Not running in a guest VM context - this vulnerability specifically affects the Linux guest VM's D-Bus configuration, not the hypervisor host
Inspect D-Bus configuration for NVIDIA services

Look for D-Bus configuration files in /etc/dbus-1/system.d/ or /usr/share/dbus-1/system.d/ related to NVIDIA (nvidia*,vgpu*) and check for <allow> rules that permit anyocal or unauthenticated access to protected endpoints

Affected if D-Bus config files contain overly permissive rules allowing unauthorized users access to protected NVIDIA D-Bus services

A system is affected if it runs an NVIDIA vGPU guest driver in a virtual machine with a version matching the affected ranges AND has overly permissive D-Bus configuration allowing unauthorized access to protected endpoints.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 11.11 / 13.6 / 14.4 or later

Fixed in 11.1113.614.4

Interim mitigation

Update NVIDIA vGPU Display Driver to the latest version containing the patched D-Bus configuration that properly restricts access to protected endpoints. Verify that unauthorized users in guest VMs can no longer access protected D-Bus services.

Recommended fix High confidence

NVIDIA vGPU Display Driver: upgrade to 470.161.03 (or newer), 510.108.03 (or newer), or 450.216.04 (or newer); Virtual GPU: upgrade to 11.11, 13.6, 14.4 or newer; Cloud Gaming: upgrade to 525.60.12 or newer

Identify the current NVIDIA vGPU Display Driver version installed on the Linux guest VM using 'nvidia-smi' or package manager
Download the appropriate fixed driver version from NVIDIA's official website (nvidia.com) based on your product: Gpu Display Driver >= 470.161.03, 510.108.03, or 450.216.04; Virtual Gpu >= 11.11, 13.6, or 14.4; Cloud Gaming >= 525.60.12
Stop any running virtual machines if upgrading the hypervisor-level vGPU software
Install the updated driver package using the NVIDIA installer (e.g., './NVIDIA-Linux-x86_64-xxx.run' or package manager for your distribution)
Verify the driver loaded successfully by running 'nvidia-smi' and confirming the driver version matches the expected fixed release
Reboot the guest VM to ensure all D-Bus services load with the updated configuration

Caveat Review NVIDIA's driver release notes for any functionality changes between your current and target version; some legacy vGPU features may have been deprecated

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
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

12.0 hours of engineering $2,080

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

nvidia.custhelp.comVendor Advisory
security.gentoo.orgThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42260 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-42260?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 11.11 / 13.6 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Gpu Display Driver

Remediation

A high-priority fix

Fix this in Gpu Display Driver 12 hrs · Moderate

Typical engagement from $2,080

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-42260 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References