CVE-2026-74453 json
drm/vc4: Zero the tile state data array before each BIN job
published 2026-08-15 2 mo ago modified 2026-10-16 23 d ago also EUVD-2026-59646
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.105-1
- linux Debian 14 7.1.8-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-74453
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1113.119
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1111.115
ubuntu advisories UBUNTU-CVE-2026-74453
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.84.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.84.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.84.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1
- kernel-obs-build SLE Module for Development Tools 15 SP7 6.4.0-150700.53.84.1
- kernel-default-base SLE Module for Basesystem 15 SP7 6.4.0-150700.53.84.1.150700.17.47.1
suse advisories SUSE-SU-2026:4706-1SUSE-SU-2026:4687-1SUSE-SU-2026:4668-1SUSE-SU-2026:4667-1SUSE-SU-2026:4666-1SUSE-SU-2026:4665-1
- git.kernel.org/stable/c/c5d8e8e1a8e3b4e464683c5a8a869c16a6382fea commit
- git.kernel.org/stable/c/d3677372e0275e139f0efd2872c5a524b5d12868 commit
- git.kernel.org/stable/c/c8dea7e7c6098e383e44f21a64d0431da5480e3f commit
- git.kernel.org/stable/c/f5802be65535f8818af7191159cf8c11f48ab2a2 commit
- git.kernel.org/stable/c/0e858422df2334165293ea742da9fbb2e51f2739 commit
- git.kernel.org/stable/c/57667eb7548faaac396c6e39f3b4444dab5b097c commit
- git.kernel.org/stable/c/a75c8f365e209aa9bb927b0942a7840152d44892 commit
- git.kernel.org/stable/c/48a570c964d8e37d353381e4195106277e17f5cb commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-74453 updated cvss 5.5
kernel: drm/vc4: Zero the tile state data array before each BIN job
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/c5d8e8e1a8e3b4e464683c5a8a869c16a6382fea
- git.kernel.org /stable/c/d3677372e0275e139f0efd2872c5a524b5d12868
- git.kernel.org /stable/c/c8dea7e7c6098e383e44f21a64d0431da5480e3f
- git.kernel.org /stable/c/f5802be65535f8818af7191159cf8c11f48ab2a2
- git.kernel.org /stable/c/0e858422df2334165293ea742da9fbb2e51f2739
- git.kernel.org /stable/c/57667eb7548faaac396c6e39f3b4444dab5b097c
- git.kernel.org /stable/c/a75c8f365e209aa9bb927b0942a7840152d44892
- git.kernel.org /stable/c/48a570c964d8e37d353381e4195106277e17f5cb
Sources
- CVE List CVE-2026-74453
- NVD CVE-2026-74453
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.