CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups
In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Skip CSD when it has zeroed workgroups
A compute shader dispatch encodes its workgroup counts in the CFG0..CFG2 registers. Kicking off a dispatch with a zero count in any of the three dimensions is invalid. First, the hardware will process 0 as 65536, while the user-space driver exposes a maximum of 65535. Over that, a submission with a zeroed workgroup dimension should be a no-op.
These zeroed counts can reach the dispatch path through an indirect CSD job, whose workgroup counts are only known once the indirect buffer is read and may legitimately be zero, but such scenario should only result in a no-op.
Overwrite the indirect CSD job workgroup counts with the indirect BO ones, even if they are zeroed, and don't submit the job to the hardware when any of the workgroup counts is zero, so the job completes immediately instead of running the shader.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Update the Linux kernel DRM/v3d driver to a version where CSD dispatches are skipped when the indirect compute shader workgroup counts (CFG0..CFG2) are zeroed, so that no shader job is submitted to hardware when any workgroup dimension is invalid/zero.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53139?
The severity of CVE-2026-53139 is medium with a CVSS score of 5.5.
How do I fix CVE-2026-53139?
To fix CVE-2026-53139, update your Linux kernel to the latest version where this vulnerability is resolved.
What systems are affected by CVE-2026-53139?
CVE-2026-53139 affects systems running the Linux kernel, specifically those utilizing the drm/v3d module.
What is the description of CVE-2026-53139?
CVE-2026-53139 describes an issue in the Linux kernel where a compute shader dispatch with zeroed workgroups is invalid and can lead to potential vulnerabilities.
Is CVE-2026-53139 a critical vulnerability?
CVE-2026-53139 is not classified as critical but has a medium severity rating, indicating it should still be addressed promptly.