# CVE-2026-53139: drm/v3d: Skip CSD when it has zeroed workgroups

> A local attacker can cause a denial of service by submitting a compute shader dispatch with zeroed workgroup counts, leading to unexpected hardware behavior.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 4 Jul 2026
- **Also known as:** BELL-CVE-2026-53139, DEBIAN-CVE-2026-53139, GHSA-qcxp-rj5j-4rr9, ROOT-OS-DEBIAN-11-CVE-2026-53139, ROOT-OS-DEBIAN-12-CVE-2026-53139, ROOT-OS-DEBIAN-13-CVE-2026-53139, ROOT-OS-UBUNTU-2204-CVE-2026-53139, ROOT-OS-UBUNTU-2404-CVE-2026-53139, UBUNTU-CVE-2026-53139

## What is CVE-2026-53139?

CVE-2026-53139 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-53139?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53139?

Apply the vendor's patch.

## Is CVE-2026-53139 being exploited?

There is no known exploitation of CVE-2026-53139 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53139 and fix it if it is affected.

What it is: CVE-2026-53139 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53139 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53139/ (Markdown: https://insights.sbomify.com/CVE-2026-53139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53139
- OSV: https://osv.dev/vulnerability/CVE-2026-53139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53139/
Summaries are generated and may contain mistakes; the official description above is the record.