CVE-2022-34682

What it actually does

An unprivileged local user can trigger a null-pointer dereference in the kernel-mode display driver layer, resulting in a kernel crash and denial of service.

Why it matters to the business

Affected GPU-accelerated and virtualized systems may suffer unplanned downtime, interrupting workloads on Linux hosts, hypervisors, and cloud gaming platforms until the system is rebooted.

How an attack unfolds

An attacker with local user access runs code or a program that exercises the vulnerable kernel driver path, causing the null dereference and immediate system instability or reboot.

How to fix it

Install the latest NVIDIA GPU Display Driver updates for Linux and apply corresponding fixes from vendors including Red Hat, VMware, and Citrix for their respective virtualization layers.

How to confirm the fix worked

Confirm updated driver versions are deployed, review kernel logs for absence of null-dereference oops entries under NVIDIA modules, and perform regression testing with GPU workloads.

Typical attack path

1. Obtain local unprivileged access on an affected Linux system
2. Execute code or trigger driver operations that reach the flawed kernel routine
3. Induce kernel null-pointer dereference leading to crash or DoS

How to detect it

Inspect kernel logs and dmesg for null-pointer dereference messages involving NVIDIA kernel modules; correlate with user-initiated GPU operations preceding the crash.

• BUG: unable to handle kernel NULL pointer dereference
• NVRM.*null pointer
• nvidia.*oops

What your security team should do

• Prioritize driver updates on all affected NVIDIA Linux and virtualized deployments
• Limit local user privileges on GPU hosts where feasible
• Enable kernel crash reporting and monitor for related oops messages