Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53139, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d223f98f02099b002903b9b22b56febae16ef80d – < b3a8dd72b0d008ff142880b4dbe5ca37dcf962b4
    • affected d223f98f02099b002903b9b22b56febae16ef80d – < 8b51c5406ad748c3d5575b66b6009b5dbbc08b80
    • affected d223f98f02099b002903b9b22b56febae16ef80d – < abb069fdf51a9ddabcc1ed125dafe54e2089900b
    • affected d223f98f02099b002903b9b22b56febae16ef80d – < ad166139d123dc162e8636f0c7962516d04074e1
    • affected d223f98f02099b002903b9b22b56febae16ef80d – < 9655b56b6de918e1c22b92f3880ae41b052cbd00
    • affected d223f98f02099b002903b9b22b56febae16ef80d – < 11e6432836394e00d39e468cd514f9ddb66f1e49
    • affected d223f98f02099b002903b9b22b56febae16ef80d – < 7f93fad5ea0affc9e1505dd0f7596c0fdb496213
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53139 badge
[![CVE-2026-53139](https://cveledger.app/badge/CVE-2026-53139.svg)](https://cveledger.app/cve/CVE-2026-53139)

Record last updated .