From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154036; b=yuFrvHVzD8HthTDf7uqRgMNVv5PmNKnYOYw/IanP0y2f+m2vCqwzUXunkJWKjAmEnEaB 2GN8nFFSMZzq3nrZKs82Y0cVJpekgYM5GXGRdcrn2PywNrT0j4dBzJVEmfY9xvIrgMVaI B1RDyarZDecXIhZXq3V45F7Jy2V/9y4zmc17tECrs4UyxsKJ+TQEARhxbOSi9PzgS6Wbj vihJj27OmwgKDwLrcWD74XVz4DUwDBxymPKmTqaeyLXmyT8uMWS7yiew1f6uDba6uAANJ dDW4zX2tquh3HMi/5YnQrIpPvGVKgyQJQTVKX7jKyOkV9WEJOTOnl9mcCKvdimLAFMQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154036; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=ANtOiwzbADQ2dSppmT3T3rhqh/tpewzlYS6jljlL01w=; b=W2l5IzjBO3Cpy/9OHibUGEhw2WGHeObX3rNi3JENmsgiip3HHBzLdMND/woX4Bu1eOEa l0aMpGfTZ5Btc/QE4M2Gezq4fd7dTq8TgwBvkR1YBzHHtrnUaLfQZi6Sm7Y7hLY9d2038 EgWoH7/CCjYMnWLLzRgUwPGy14cQ93MumsYre7hogUAgqzhGVJE8lOqBJIEbH0gccGPTX 7pn2G/RCjCbiZKqXtpLCLEniKm5Zt2g2lNGDphj+T3SNue7HSsKgv6pthyMpe3nK3Q6RL r1LF2S8WbH+Q9Ds6tVRH0hTQTn5Ku5yjzGyhli7O38ha4mMYBU5qKzj7FxArgpc0GSw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=tOPhfJEx; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A89C2606A320 for ; Fri, 20 Nov 2026 05:53:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=tOPhfJEx Received: by smtp.kernel.org (Postfix) with ESMTPSA id 008421F000C6; Fri, 20 Nov 2026 05:53:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154036; bh=ANtOiwzbADQ2dSppmT3T3rhqh/tpewzlYS6jljlL01w=; h=From:To:Cc:Subject:Date:Reply-To; b=tOPhfJExIX4qx9uQ3YpT4v2tJcV1PkFzswPSo/OVhGJPg/jrtS6iQFbf5ZNpYWC7Q +fxhBZ/jdQDqfRljmauPAqsRaYpPDD8FYpVksyoI2ITqTfwpF/DhWU9Rl35Ytf3z/M 2TBgLSQ8IcwFj+/lGxzP974JATeGroLDZaA0O1Oc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman 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 Message-ID: <2026112027-CVE-2026-99604-66ae@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3487; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=jOmPAxi8EQch0yo/Tkbx9GLLctlHqli1xlUlQsILDZc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/76eLcM/kmhH237FZedLb6oKbDukM2QX+/lfbp6341 Lac78OijlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIEg/Dgr69zgJ53Oe35aZ+ WCZ5+LbQJSWtHwzzFFqMk+TWZx7kOsiVannvS8fdWWtNAQ== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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