Skip to content
VulniPulse
Sign in
Advisory severityUnratedRed Hat Linux

Advisory [CVE-2026-53139] Skip CSD when it has zeroed workgroups

This Red Hat Linux security advisory covers CVE-2026-53139.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-53139 Source published Source updated

VulniPulse record published Record updated

CVE-2026-53139
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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. A flaw was found in the Linux kernel's graphics driver for Broadcom V3D (VideoCore V) GPUs.

This vulnerability occurs when a compute shader dispatch (CSD) is initiated with zero workgroup counts, which the hardware could misinterpret as a very large number. This misinterpretation could lead to unexpected system behavior or a denial of service (DoS), where the system becomes unresponsive or crashes.

Red Hat severity: not rated. Weakness: CWE-1284.

Is CVE-2026-53139 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-53139 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-53139?

The advisory VulniPulse tracks names no fixed release. Follow Red Hat's guidance for workarounds and updates.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · medium-confidence parse· fetched 15 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 15 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That does not mean no fix exists. Read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 15 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat

More Red Hat Linux advisories

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.