# CVE-2026-74453: drm/vc4: Zero the tile state data array before each BIN job > Attackers can read stale GPU memory or cause hangs because the kernel fails to clear tile state data between jobs. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Aug 2026 - **Updated:** 16 Oct 2026 - **Also known as:** AZL-95991, BELL-CVE-2026-74453, DEBIAN-CVE-2026-74453, GHSA-3p68-w4fc-v365, UBUNTU-CVE-2026-74453 ## What is CVE-2026-74453? CVE-2026-74453 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. ## Which versions are affected by CVE-2026-74453? ## How do I fix CVE-2026-74453? Apply the vendor's patch. ## Is CVE-2026-74453 being exploited? There is no known exploitation of CVE-2026-74453 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-74453 and fix it if it is affected. What it is: CVE-2026-74453 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-74453 in the wild and no public exploit code. Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-74453/ (Markdown: https://insights.sbomify.com/CVE-2026-74453/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74453 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74453 - OSV: https://osv.dev/vulnerability/CVE-2026-74453 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-74453/ Summaries are generated and may contain mistakes; the official description above is the record.