CVE-2026-53139
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.211
- Linux Kernel < 6.1.177
- Linux Kernel < 6.6.144
- Linux Kernel < 6.12.95
- Linux Kernel < 6.18.36
- Linux Kernel < 7.0.13
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53139.md and follow it. Check whether this project is affected by CVE-2026-53139. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/11e6432836394e00d39e468cd514f9ddb66f1e49
- https://git.kernel.org/stable/c/7f93fad5ea0affc9e1505dd0f7596c0fdb496213
- https://git.kernel.org/stable/c/8b51c5406ad748c3d5575b66b6009b5dbbc08b80
- https://git.kernel.org/stable/c/9655b56b6de918e1c22b92f3880ae41b052cbd00
- https://git.kernel.org/stable/c/abb069fdf51a9ddabcc1ed125dafe54e2089900b
- https://git.kernel.org/stable/c/ad166139d123dc162e8636f0c7962516d04074e1
- https://git.kernel.org/stable/c/b3a8dd72b0d008ff142880b4dbe5ca37dcf962b4
References
- https://git.kernel.org/stable/c/11e6432836394e00d39e468cd514f9ddb66f1e49
- https://git.kernel.org/stable/c/7f93fad5ea0affc9e1505dd0f7596c0fdb496213
- https://git.kernel.org/stable/c/8b51c5406ad748c3d5575b66b6009b5dbbc08b80
- https://git.kernel.org/stable/c/9655b56b6de918e1c22b92f3880ae41b052cbd00
- https://git.kernel.org/stable/c/abb069fdf51a9ddabcc1ed125dafe54e2089900b
- https://git.kernel.org/stable/c/ad166139d123dc162e8636f0c7962516d04074e1
- https://git.kernel.org/stable/c/b3a8dd72b0d008ff142880b4dbe5ca37dcf962b4