From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E45514F7965 for ; Wed, 16 Sep 2026 10:36:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555003; cv=none; b=KBv6aX/o/LmGRNBBHfEuIaOaco7rb5irhA6ORwVVHPomZuS5sBDuZlu+cucxW0lMpLBUviJtkHs2VaXwDd/GfKYdvvuWgsoE7DRAY2NWDUyMoEsOia2JJlEoco5EZkQg7WbjQzWRrG7C5rHRPWZpoQPnqrnsVFtvaD7tYyOAPjk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555003; c=relaxed/simple; bh=C7ubK1iE9f1ptBp6PP6cv4bOQjJvOvMbFtl6hjLIop0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=PgOgqxKY088BnlNo1DbC10dbbLhEvfLRwpZLYCMEWLRIe5wx2/k642KEgzYlsyJqwn1/0o7pZSSYfTQqYVKeTN4SM0AyAGXhOZcMv8jWhZK44oGOOYa6WC90m7C6gIqHZNQkqjdxqnqPXhRdpIAZHx5lqzLWtxbyvG2445etJWQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=l8BXMzLy; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="l8BXMzLy" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C2E921F0089B; Wed, 16 Sep 2026 10:36:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789554977; bh=m2aj6VQD3TDrVL8OwrXq5oD3sx6prPDK14umKF3tTNA=; h=From:To:Cc:Subject:Date:Reply-To; b=l8BXMzLyb8DLf/3CMXAIdsJgRUu2YWufXTXEnX8HV8MTas28u0sLoiHqpN7uG7HEf 9k34U7+Dy9mIpDejvLjLv3wl0STnlndwv5fpmvyWJswoAVGi3Fd9M3YgXYzcqR2Ma2 7KXUAIrl0qAlcaDRAjlEUSv7BZxSvakog0LNxu+U= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89866: media: chips-media: wave5: Resume device before setting EOS flag Date: Wed, 16 Sep 2026 11:29:56 +0100 Message-ID: <2026091623-CVE-2026-89866-bdca@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2768; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=lxr1eNWJdxEHG6rhy23E6f18OZAo2J0DKFSZ1r1LuFc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8luUHO8LVmk9XCjvf/z4/adR989u9rXiTsi7sNRUg qVGtt6pI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACbyt5thfoGrWaaXnlSqohGP 8rQmp3w/HtctDPM9X1s3fVBVlYx2OJ+gPy+8eJ/q7B4A 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: media: chips-media: wave5: Resume device before setting EOS flag Setting the EOS flag talks to the firmware via send_firmware_command(), which accesses VPU registers. Both the STREAMOFF path (wave5_vpu_dec_job_abort()) and the V4L2_DEC_CMD_STOP path (wave5_vpu_dec_stop()) can run while the device is runtime suspended, so those register accesses hit powered-down hardware and the SoC raises an asynchronous SError, panicking the kernel: SError Interrupt on CPU3, code 0x00000000bf000000 -- SError send_firmware_command+0x2c/0x160 [wave5] wave5_vpu_dec_set_bitstream_flag+0x6c/0x80 [wave5] wave5_vpu_dec_update_bitstream_buffer+0x80/0xec [wave5] wave5_vpu_dec_job_abort+0x44/0xa0 [wave5] v4l2_m2m_cancel_job+0x110/0x19c [v4l2_mem2mem] v4l2_m2m_streamoff+0x24/0x140 [v4l2_mem2mem] Resume the device with pm_runtime_resume_and_get() around the EOS firmware command and release it with pm_runtime_put_autosuspend(), matching the runtime PM handling already done in wave5_vpu_dec_device_run(). The Linux kernel CVE team has assigned CVE-2026-89866 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit 9707a6254a8a6b978bde811a44fe07d86c229d1c and fixed in 7.2.5 with commit 2215e55ee1e5e69ad53862d968360c5aa63dd3a7 Issue introduced in 6.8 with commit 9707a6254a8a6b978bde811a44fe07d86c229d1c and fixed in 7.3-rc1 with commit a52e6f7923c17a672135b485ffd96fbd72f46267 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-89866 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/media/platform/chips-media/wave5/wave5-vpu-dec.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/2215e55ee1e5e69ad53862d968360c5aa63dd3a7 https://git.kernel.org/stable/c/a52e6f7923c17a672135b485ffd96fbd72f46267