CVE-2026-99604: Linux kernel · drm/etnaviv: Flush the tile status cache through both the PE and BLT
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e75d39dc2a4dbfa6064bd7e59e0cf5d3d1b89b6d : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:19 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e75d39dc2a4dbfa6064bd7e59e0cf5d3d1b89b6d, c1a757f8df1363032623fa9b1baaba0dcf34de6d, 8cd026a2cec3e4ceb4542ba443d9049724ae4a30 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: drm/etnaviv: Flush the tile status cache through both the PE and BLT Since commit f232d9ec029c ("drm/etnaviv: fix TS cache flushing on GPUs with BLT engine"), jobs on GPUs with a BLT engine use a BLT command to flush the tile status cache instead of TS_FLUSH_CACHE, which is broken on most of these GPUs. GC7000 r6008/r6009 and GC8200 r6401 are the other way around: TS_FLUSH_CACHE works, but the BLT command does not flush the cache. The vendor driver handles these GPUs using TS_FLUSH_CACHE, but the etnaviv kernel driver has no way to identify them. As a result, dirty tile status cache lines survive the end of a job. They are written back by the next cache flush, using the page table of the job issuing it. If that job belongs to another process, the write goes to the wrong address space. On GC7000 r6009 this causes MMU faults and GPU recoveries blamed on an innocent process. I see around 1100 per run of a multisample depth/stencil test running alongside two other GPU clients. Emit both flushes at the end of every job on GPUs with a BLT engine. Whichever does not work on a given GPU is a no-op. Since dirty lines are only written back once, this costs one additional state load per job.
References
- git.kernel.org/stable/c/0abbe840a90d2cb568781fd031e514674c397cff (opens in a new tab)
- git.kernel.org/stable/c/8cd026a2cec3e4ceb4542ba443d9049724ae4a30 (opens in a new tab)
- git.kernel.org/stable/c/e75d39dc2a4dbfa6064bd7e59e0cf5d3d1b89b6d (opens in a new tab)
- git.kernel.org/stable/c/c1a757f8df1363032623fa9b1baaba0dcf34de6d (opens in a new tab)