Home/CVE/NVIDIA vGPU Display Driver for Linux guest contains a vulnerability in a D-Bus configuration file, where an unauthorized
CVE

CVE-2022-42260

NVIDIA vGPU Display Driver for Linux guest contains a vulnerability in a D-Bus configuration file, where an unauthorized

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.

HIGH · CVSS 7.8 EPSS 0.00212
Schedule remediation
  • CVSS base score ≥ 7.0
Sigma rules3 YARA rules0
⬡

Weakness Classification

CWE-281Improper Preservation of Permissions
▤

Affected Products & Versions

8
nvidia virtual gpu< 11.11
nvidia virtual gpu>= 12.0 and < 13.6
nvidia virtual gpu>= 14.0 and < 14.4
nvidia cloud gaming< 525.60.11
nvidia gpu display driver>= 470 and < 470.161.03
nvidia gpu display driver>= 510 and < 510.108.03
nvidia gpu display driver>= 450 and < 450.216.04
nvidia cloud gaming< 525.60.12
◈

Sigma Hunt Rules

3
Exact rules name this CVE ID. Product rules name an affected product in their title. Related rules cover techniques used by actors who exploited this CVE. Showing the most relevant matches; the complete related set is on the full drill-down.
producthighHypervisor-protected Code Integrity (HVCI) Related Registry Tampering Via CommandLine
producthighWindows Hypervisor Enforced Code Integrity Disabled
producthighHypervisor Enforced Paging Translation Disabled
▣

Scoring & Timeline

7.8
HIGH · CVSS v3.1 · psirt@nvidia.com
View on NVD
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
Published to NVD30 Dec 2022 · 11:15 PM
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Technical impact
total
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
🔗

References & Sources

2
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://nvidia.custhelp.com/app/answers/detail/a_id/5415Vendor Advisory
https://security.gentoo.org/glsa/202310-02Third Party Advisory
Intelligence Graph · click any node to traverse
CVETechnique ActorTool Family
drag to reposition · click any node to traverse · button top-right enlarges
External lookups - second-class, for what we don’t hold ourselves
NVDCVE.orgCISAVulnersExploit-DBGitHub PoCVulnCheck KEVGreyNoise
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh  ·  Open-source threat intelligence platform  ·  100+ authoritative sources  ·  Every fact traces to its origin