The flaw in the Linux kernel's drm/vc4 driver occurs when the BO cache size list is not freed during teardown by vc4_bo_cache_destroy(). The list is purged, but its size list is never released, leaking that memory on every unbind. This memory leak flaw (CWE-772) can gradually exhaust system memory if the VC4 device is repeatedly bound and unbound, potentially leading to out‑of‑memory conditions or degraded system responsiveness.

All Linux kernel builds that include the drm/vc4 driver without the recent patch are affected. No specific kernel release is enumerated, so any system running the unpatched drm/vc4 module is vulnerable. The issue resides purely in the driver code, not in user space applications.

The EPSS score is < 1%, indicating an extremely low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The flaw requires an unbind of the VC4 device, which typically occurs through user‑space libraries or drivers. The likely attack vector is local and may be exercised by a privileged or compromised application. Although the probability of exploitation is very low, the memory leak can lead to gradual exhaustion of system resources, potentially resulting in a denial‑of‑service. The overall risk assessment remains low, but patching remains the recommended action.