Description
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Clear queue->active_job when v3d_fence_create() fails The run_job() callbacks for BIN, RENDER, TFU and CSD assign the incoming job to queue->active_job before calling v3d_fence_create(). If v3d_fence_create() fails, the callback returns NULL without clearing active_job, leaving a dangling pointer. Create a failure path in all run_job() callbacks that clears the active job before returning NULL. The BIN path takes queue->queue_lock around the clear as it races against v3d_overflow_mem_work(); RENDER, TFU and CSD paths have no concurrent reader, so the clear is lock-free.
References6
- git.kernel.org/stable/c/0b9878aba5cf93bc2b55ba9eb807757ce3239bec
- git.kernel.org/stable/c/1f661f42beb558b2d21882f0cd527ed6c8e7e749
- git.kernel.org/stable/c/25a1669907512e927fab9ad4d4fb74ff57f63cd9
- git.kernel.org/stable/c/3a8aa74859dd73eaa76c55eb74da708e56ef51c5
- git.kernel.org/stable/c/bdeb73d7312100e00c3e643ff233f09b6ec114aa
- git.kernel.org/stable/c/dc0fba19ef518920073d1d639317b2dd8266fe5e
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 7 · as of 8 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.