CVE-2026-99605 in Linuxinfo

Summary

by MITRE • 11/20/2026

In the Linux kernel, the following vulnerability has been resolved:

drm/etnaviv: Fix NULL dereference on unbind without PPU flop reset

flop_reset_data_ppu is only allocated on GPUs that need the PPU flop reset. However, etnaviv_unbind(..) frees it unconditionally, and etnaviv_cmdbuf_free(..) 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The Linux kernel's DRM etnaviv driver contains a critical memory management flaw related to conditional resource allocation and unconditional deallocation during device unbinding operations. This vulnerability specifically affects systems utilizing GPUs that do not require the PPU flop reset mechanism, which is a specific hardware initialization or recovery procedure handled by the driver. The root cause lies in an asymmetry between how resources are allocated and how they are freed within the driver's lifecycle management functions. Specifically, the data structure flop_reset_data_ppu is conditionally allocated only for GPUs that explicitly need this particular reset functionality. However, when the device is being unbound from the system, typically during module removal or hot-unplug scenarios, the etnaviv_unbind function proceeds to free this memory buffer without verifying whether it was actually allocated in the first place. This unconditional freeing of a NULL pointer constitutes an improper resource cleanup pattern that leads directly to kernel instability.

The operational impact of this vulnerability manifests as a null pointer dereference when the driver is unloaded on affected hardware configurations. Because flop_reset_data_ppu remains NULL for GPUs not requiring the PPU flop reset, attempting to free it results in the kernel trying to release memory at address zero or an invalid location depending on how the underlying allocator handles such inputs, often triggering a page fault or oops condition. This effectively causes a denial of service by crashing the kernel process responsible for driver management and potentially destabilizing the entire system if not contained properly. Furthermore, within the command buffer handling logic, there is a secondary issue where etnaviv_cmdbuf_free attempts to dereference cmdbuf->suballoc before performing a null check on the cmdbuf pointer itself. This ordering error means that even if other parts of the code path are safe, this specific function can crash when passed a NULL context, further exacerbating reliability issues during driver teardown or command buffer cleanup operations.

From a vulnerability classification perspective, this issue aligns with CWE-476, which denotes a NULL Pointer Dereference. This type of flaw occurs when software dereferences a pointer that it expects to be valid but is actually null, leading to crashes or potential exploitation vectors if the attacker can control the memory state around address zero. In terms of attack vector and technique mapping under MITRE ATT&CK for Enterprise, this vulnerability relates to T1059 Command and Scripting Interpreter through indirect means, as kernel panics caused by driver bugs are often leveraged in local privilege escalation chains or used to disrupt availability services. The lack of proper null checks before memory access violates fundamental secure coding practices regarding defensive programming against invalid pointer states.

To mitigate this vulnerability, the primary remediation involves correcting the logic within etnaviv_unbind and related cleanup functions to ensure that resources are only freed if they were successfully allocated. Developers must implement explicit conditional checks prior to calling free or equivalent deallocation routines for flop_reset_data_ppu. Additionally, in etnaviv_cmdbuf_free, the null check on cmdbuf must be performed before any attempt to access its members such as suballoc. These fixes ensure that the driver gracefully handles devices with varying hardware capabilities without assuming uniform resource availability across all GPU models supported by the same codebase. System administrators should apply kernel updates containing these patches immediately upon release to prevent potential system crashes during routine maintenance tasks involving driver unloading or device removal on affected etnaviv-based graphics hardware.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00156

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!