CVE-2026-74453

published 15 Aug 2026 · updated 15 Nov 2026

drm/vc4: Zero the tile state data array before each BIN job

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f5802be65535f8818af7191159cf8c11f48ab2a2, Kernel 0e858422df2334165293ea742da9fbb2e51f2739, Kernel 48a570c964d8e37d353381e4195106277e17f5cb and 12 more.

In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Zero the tile state data array before each BIN job The binner BO is a single 16MB buffer split into 512KB slots that are handed out to jobs at submission time and recycled as jobs complete, without ever being cleared. Each slot holds the job's Tile State Data Array (TSDA) at its start, followed by the tile allocation pool. While the tile allocation pool is only walked by the render thread through branches the binner generated during the current job, the TSDA is the PTB's own per-tile bookkeeping and is consumed by the hardware itself. Although the kernel sets the "Auto-initialise Tile State Data Array" flag in the tile binning mode configuration, the PTB demonstrably still acts on stale tile state left by the slot's previous user: the binner ends up creating invalid command streams with invalid primitive streams and branches, which can cause GPU hangs as observed in [1][2]. Zero the TSDA when the job's binning slot is configured. This clears 48 bytes per tile (~24KB for a 1080p frame) in the submission path, and guarantees the PTB never sees another job's tile state. The tile count is only checked for being non-zero today, so the 8-bit fields it comes from can describe a tile state array almost six times larger than the slot it has to live in. Bound it before the slot is handed out, since such size decides how much of the slot is left for the tile alloc pool.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <f5802be65535f8818af7191159cf8c11f48ab2a2, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <0e858422df2334165293ea742da9fbb2e51f2739, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <48a570c964d8e37d353381e4195106277e17f5cb, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <57667eb7548faaac396c6e39f3b4444dab5b097c, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <a75c8f365e209aa9bb927b0942a7840152d44892, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <c5d8e8e1a8e3b4e464683c5a8a869c16a6382fea, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <c8dea7e7c6098e383e44f21a64d0431da5480e3f, >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <d3677372e0275e139f0efd2872c5a524b5d12868, =4.13f5802be65535f8818af7191159cf8c11f48ab2a2, 0e858422df2334165293ea742da9fbb2e51f2739, 48a570c964d8e37d353381e4195106277e17f5cb, 57667eb7548faaac396c6e39f3b4444dab5b097c, a75c8f365e209aa9bb927b0942a7840152d44892, c5d8e8e1a8e3b4e464683c5a8a869c16a6382fea, c8dea7e7c6098e383e44f21a64d0431da5480e3f, d3677372e0275e139f0efd2872c5a524b5d12868
linux-kernel: Kernel>=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.44, >=6.19.0 <7.1.8, >=6.2.0 <6.6.151, >=6.7.0 <6.12.103, >=4.13.0 <5.10.2655.15.216, 6.1.183, 6.18.44, 7.1.8, 6.6.151, 6.12.103, 5.10.265

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74453 severity on Zeptric[![CVE-2026-74453](https://zeptric.io/badge/cve/CVE-2026-74453.svg)](https://zeptric.io/cve/CVE-2026-74453)