drm/v3d: Clear queue->active_job when v3d_fence_create() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a783a09ee76d6259296dc6aeea2b6884fa526980 · < 25a1669907512e927fab9ad4d4fb74ff57f63cd9| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel’s drm/v3d driver, BIN, RENDER, TFU, and CSD job callbacks can leave a dangling active-job pointer if v3d_fence_create() fails. The input does not specify how an attacker could trigger the failure or whether access, authentication, or user interaction is required.
Teams running Linux kernels with the drm/v3d driver should check their exposure; affected versions are not specified.