From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99604: drm/etnaviv: Flush the tile status cache through both the PE and BLT
Date: Fri, 20 Nov 2026 06:49:50 +0100 [thread overview]
Message-ID: <2026112027-CVE-2026-99604-66ae@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-99604 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit f232d9ec029ce3e2543b05213e2979e01e503408 and fixed in 6.12.118 with commit 0abbe840a90d2cb568781fd031e514674c397cff
Issue introduced in 5.7 with commit f232d9ec029ce3e2543b05213e2979e01e503408 and fixed in 6.18.64 with commit 8cd026a2cec3e4ceb4542ba443d9049724ae4a30
Issue introduced in 5.7 with commit f232d9ec029ce3e2543b05213e2979e01e503408 and fixed in 7.3.5 with commit e75d39dc2a4dbfa6064bd7e59e0cf5d3d1b89b6d
Issue introduced in 5.7 with commit f232d9ec029ce3e2543b05213e2979e01e503408 and fixed in 7.4-rc2 with commit c1a757f8df1363032623fa9b1baaba0dcf34de6d
Issue introduced in 5.4.63 with commit 538caddbe635d3ca18e0f02276e76c124eb3c604
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99604
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/etnaviv/etnaviv_buffer.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/0abbe840a90d2cb568781fd031e514674c397cff
https://git.kernel.org/stable/c/8cd026a2cec3e4ceb4542ba443d9049724ae4a30
https://git.kernel.org/stable/c/e75d39dc2a4dbfa6064bd7e59e0cf5d3d1b89b6d
https://git.kernel.org/stable/c/c1a757f8df1363032623fa9b1baaba0dcf34de6d
reply other threads:[~2026-11-20 5:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112027-CVE-2026-99604-66ae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.