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=1792758552; b=I23HDzM5XApI5ZDGRwHYHnl0xa8MggPoKwbnrYI4fKevVH07YxRlmx1ZwrCqE9L/bPh9 Zp0fC/DsbRW1xZ7Yvy27EbgNmbWVgPghwYUMDDI6d6R/uhAhVD083hv0/PAhabykG77i8 1eOZEx+Kl0GyoFiIJ6VLNdj5+ix774316EpuAOsf9bp6l9mIquhuSqvk6IYf81rn9y5D1 Ge1KBwyT3kko5htZaEaE0QTOZOiqkP/b/rU7F6O+GkfM/AS71hs0ECb5geYow8KXupMOd UnCAoOMAZg/DUkM0cmzQvDSigej0SSau7h4m76VVTExmmE4qhc0ntYnIZ72WnWPSW0w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792758552; 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=YnntNJJED4KDO9DrhJ5UloA7xGZLbALQYuvgbzGxhVU=; b=T6O6SLJnYgjOXkA7Mbj77t7iTAoO9yPN1z1Tn0nZ5BCf9zwVEqHwNlMALLD9Fl9KgB9i Y8EIrIGICVUBI4IHPqWhldsbfV2qMF5aJ4eGpljcARBpTbCSI5VZR661FELTsXEFefPx0 bplXBXaIXMlnnxs0Id+ZoyPazyA/IVP7g+RjZ6P72BrZgCvYqQdSdyiaTLzavP/PvHzM2 OAtxNXU3TmmBGK2vuLTMsohmRU5pB85VINaT5refbmhMxXY003JM9dnYAf6WtRUo4o3ab Uh+Cz3pY4LuXKn6xhg8Ugt2Z7AAPZeKotoSMScjg18GpX8YEFDA44G3NdErleCvi22g== 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=HO6voDM+; 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 5C0D1606A31A for ; Fri, 23 Oct 2026 12:29:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=HO6voDM+ Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3D79E1F01825; Fri, 23 Oct 2026 12:29:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1792758552; bh=YnntNJJED4KDO9DrhJ5UloA7xGZLbALQYuvgbzGxhVU=; h=From:To:Cc:Subject:Date:Reply-To; b=HO6voDM+8QxfGvrhr/df2pjs1eZXBWOqd9YdKF0KrjhF8DYZjEpcjnQYb4UuKcUgR UagR9N8IeA3p5Fv12X7PuTu4yUli/DuznRKHTUbUyWVWH642xYmdxfYDGYkUeGyRHw mGLhDY8DNyGmnnO+Dt/tx0LbJk9amgkOwTcQBa38= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-98946: drm/vc4: Disable the V3D interrupt across runtime suspend Date: Fri, 23 Oct 2026 14:19:08 +0200 Message-ID: <2026102305-CVE-2026-98946-9b60@gregkh> X-Mailer: git-send-email 2.56.0 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=3224; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Ub3AsdftLJcsAuII9RkTcjBnqK7P9ojYQ+xXxm/ULIU=; b=owGbwMvMwCRo6H6F97bub03G02pJDFm3A3Y+r9JdcfvnprduV4yWMrrH6/k6HL/yJccmONTi6 Q+XmT+8O2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAip/gYFqxuYJt9k+0gY0aA yrwk12kzLnr6azIsWKN+OyjynQ3D6a5Dcd2eW1f9VzcMAgA= 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/vc4: Disable the V3D interrupt across runtime suspend vc4_irq_disable() masks the V3D interrupt sources and then calls synchronize_irq() before the V3D is powered down. However, by itself, this is not enough to quiesce the interrupt handler. synchronize_irq() waits for handlers that have already set IRQD_IRQ_INPROGRESS, and for irqchips reporting IRQCHIP_STATE_ACTIVE. A GIC interrupt chip is able to mark an interrupt active as soon as a CPU acknowledges it, so there these checks cover the whole dispatch path. On RPi 0-3, however, the interrupt controller is ARMCTRL, which has no active state. A CPU that has read the hwirq out of the pending register but has not yet reached handle_level_irq() stays invisible to synchronize_irq(). During a power transition, vc4_irq() may therefore run after the power domain is off, where every V3D register read will return 0xdeadbeef. 0xdeadbeef has FLDONE, FRDONE and OUTOMEM set. This problem doesn't trigger NULL pointer dereference issues only because the functions vc4_irq_finish_bin_job() and vc4_irq_finish_render_job() return early when there is no job pointer, but OUTOMEM is still able to schedule vc4_overflow_mem_work() after vc4_irq_disable() has already cancelled it. Therefore, fix the spurious interrupts by disabling the interrupt line across the PM transition. To preserve the enable/disable balance, move vc4_irq_install() and request the IRQ line disabled before the first runtime resume. The Linux kernel CVE team has assigned CVE-2026-98946 to this issue. Affected and fixed versions =========================== Issue introduced in 6.1 with commit 9b6f461582e6b07e2ce93227a3e4661846e594ad and fixed in 7.2.11 with commit e81402c3d42041356cb7978510ebab997bc8d411 Issue introduced in 6.1 with commit 9b6f461582e6b07e2ce93227a3e4661846e594ad and fixed in 7.3 with commit 6abc8e4dcfbc1d26a94c0ac037dfb3716f686b1f 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-98946 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/vc4/vc4_irq.c drivers/gpu/drm/vc4/vc4_v3d.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/e81402c3d42041356cb7978510ebab997bc8d411 https://git.kernel.org/stable/c/6abc8e4dcfbc1d26a94c0ac037dfb3716f686b1f