CVE-2022-31608

What it actually does

Local user with basic capabilities can impact protected D-Bus endpoints via a vulnerable optional D-Bus configuration file in NVIDIA GPU Display Driver for Linux, enabling code execution, denial of service, privilege escalation, information disclosure, and data tampering.

Why it matters to the business

Systems using affected NVIDIA drivers on Linux face risk of unauthorized code execution, service disruption, privilege abuse, data leaks or tampering by local users, increasing exposure on widely deployed GPU hardware.

How an attack unfolds

A local attacker with basic access identifies the optional D-Bus configuration, then interacts with protected endpoints to abuse authorization bypass for code execution or privilege escalation.

How to fix it

Update affected packages to fixed versions: openssh (Debian:12): fixed in 1:8.9p1-1, openssh (Debian:13): fixed in 1:8.9p1-1, openssh/openssh-portable (GIT): fixed in 166456cedad3962b83b848b1e9caf80794831f0f.

How to confirm the fix worked

Verify driver package versions match fixed releases and confirm the optional D-Bus configuration file is updated or removed.

Typical attack path

1. Obtain local user access on Linux system with vulnerable NVIDIA driver
2. Locate and abuse the optional D-Bus configuration file
3. Target protected D-Bus endpoints to achieve code execution or privilege escalation

How to detect it

Review system and D-Bus logs for unusual local interactions with protected endpoints or unexpected privilege changes following NVIDIA driver usage.

What your security team should do

• Prioritize patching NVIDIA GPU Display Driver on all Linux systems
• Review and harden D-Bus configurations to restrict local access
• Monitor for local privilege escalation attempts involving D-Bus