{"id":"CVE-2026-74453","aliases":[],"url":"https://o3.security/vulnerability/CVE-2026-74453","summary":"drm/vc4: Zero the tile state data array before each BIN job","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vc4: Zero the tile state data array before each BIN job\n\nThe binner BO is a single 16MB buffer split into 512KB slots that are\nhanded out to jobs at submission time and recycled as jobs complete,\nwithout ever being cleared. Each slot holds the job's Tile State Data\nArray (TSDA) at its start, followed by the tile allocation pool.\n\nWhile the tile allocation pool is only walked by the render thread\nthrough branches the binner generated during the current job, the\nTSDA is the PTB's own per-tile bookkeeping and is consumed by the\nhardware itself. Although the kernel sets the \"Auto-initialise Tile\nState Data Array\" flag in the tile binning mode configuration, the\nPTB demonstrably still acts on stale tile state left by the slot's\nprevious user: the binner ends up creating invalid command streams\nwith invalid primitive streams and branches, which can cause GPU hangs\nas observed in [1][2].\n\nZero the TSDA when the job's binning slot is configured. This clears\n48 bytes per tile (~24KB for a 1080p frame) in the submission path, and\nguarantees the PTB never sees another job's tile state.\n\nThe tile count is only checked for being non-zero today, so the 8-bit\nfields it comes from can describe a tile state array almost six times\nlarger than the slot it has to live in. Bound it before the slot is\nhanded out, since such size decides how much of the slot is left for\nthe tile alloc pool.","published":"2026-08-15T12:26:56.949Z","modified":"2026-08-18T03:56:48.189818729Z","cvss":{"score":7.8,"severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"},"epss":null,"cisaKev":null,"exploitsKnown":null,"affectedPackages":[{"ecosystem":"Linux","name":"Kernel","fixedVersion":"6.6.151"}],"fix":null,"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0e858422df2334165293ea742da9fbb2e51f2739"},{"type":"WEB","url":"https://git.kernel.org/stable/c/48a570c964d8e37d353381e4195106277e17f5cb"},{"type":"WEB","url":"https://git.kernel.org/stable/c/57667eb7548faaac396c6e39f3b4444dab5b097c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a75c8f365e209aa9bb927b0942a7840152d44892"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f5802be65535f8818af7191159cf8c11f48ab2a2"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74453.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74453"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-08-18T03:56:48.189818729Z"}}