The vulnerability in the Linux kernel’s V3D driver arises because concurrent scheduler timeout handlers are not serialized. When a global reset is triggered by any queue, it stops and restarts all other queues’ schedulers without proper locking. This race condition allows one queue to interfere with another’s timeout handling, corrupting the credit bookkeeping and resulting in a GPU hang and UI freeze. The weakness fits the race‑condition category, where unsynchronized access to shared resources leads to an inconsistent system state.

All Linux kernel builds that include the V3D DRM driver with multiple independent hardware queues are affected. No specific version list is supplied, but the issue could exist in any kernel that has not incorporated the fix for serializing timeout handlers.

The CVSS score is not provided, and EPSS data is unavailable, so the precise exploitation probability is unknown. The bug is a local denial‑of‑service that requires an application with GPU access to trigger a timeout. An attacker with the ability to run GPU‑intensive code can cause a device reset and subsequent crash, potentially impacting system availability. The vulnerability is not listed in the CISA KEV catalog, suggesting it has not yet been widely exploited in the field.