CVE-2026-99605: drm/etnaviv: Fix NULL dereference on unbind without PPU flop reset
In the Linux kernel, the following vulnerability has been resolved:
drm/etnaviv: Fix NULL dereference on unbind without PPU flop reset
flopresetdatappu is only allocated on GPUs that need the PPU flop reset. However, etnavivunbind(..) frees it unconditionally, and etnavivcmdbuffree(..) dereferences cmdbuf->suballoc before checking whether cmdbuf is NULL.
As a result, unloading the driver on GPUs that do not need the PPU flop reset causes a NULL pointer dereference at address 0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Which systems are exposed to the crash?
Systems using the Linux kernel etnaviv DRM driver on GPUs that do not require the PPU flop reset are affected. The issue is triggered when the driver is unloaded.
Does exploitation require an unprivileged remote attacker?
The available information describes a local driver-unload path and does not identify a remote attack vector or unprivileged exploitation path. Triggering the condition requires unloading the etnaviv driver.
What happens when the vulnerable path is reached?
The driver can dereference a NULL pointer at address 0 during unbind, causing a kernel crash or fault. This occurs because PPU reset data may be absent but is freed unconditionally, and a command-buffer field is dereferenced before its NULL check.