VDB

CVE-2026-74453

CVE-2026-74453 PUBLISHED CVSS 7.8 HIGH

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

Reported by linux · Published August 15, 2026

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxf5802be65535f8818af7191159cf8c11f48ab2a2, a75c8f365e209aa9bb927b0942a7840152d44892, 57667eb7548faaac396c6e39f3b4444dab5b097c, 48a570c964d8e37d353381e4195106277e17f5cb, 0e858422df2334165293ea742da9fbb2e51f2739

Risk scores

CVSS 3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinux553c942f8b2cbc7394b4d4fa2f848b23a8f07451, 553c942f8b2cbc7394b4d4fa2f848b23a8f07451, 553c942f8b2cbc7394b4d4fa2f848b23a8f07451
LinuxLinux4.13, 0, 5.10.265
LinuxLinux6.1.183, 6.18.44, 7.1.8
linuxlinux_kernel4.13, 4.13, 4.13

Timeline

  • Aug 15, 2026 CVE Published
  • Aug 16, 2026 EPSS Score (8 in total, the first dated here)
  • Aug 19, 2026 Security Advisory
  • Oct 16, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-74453
vulnetix vdb fixes CVE-2026-74453

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-74453/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›