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 719114E80C2 for ; Wed, 16 Sep 2026 10:36:49 +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=1789555024; cv=none; b=a7DnLOnuezphvq6Wf0B8LV6I4vjZjlrtAe+xpudYYgrlCLV+JNvqC/OxbQloCnH5YcvNEwvwqSzOCGEleBRXCixQbtc1G4x57/+HNldlxl4PKuDo3dtEJ48esC/sezO6fCxeiH4k3tsv7ner9QFjjqKDHl7RqbZGmVowdqM8UF0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789555024; c=relaxed/simple; bh=J1vWcjtl5gSdNfk0sm4hz24/chfd/Uvj/UYKmeeVG/k=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=O8NTG36IU3T2ZtOysA/7DisLbEbKOYoTqui1+g39anSvcsqJZx/nxb6T+JbGcns59Z48bIivBd47fqn9Jh5kAi0O/a+DGTQPZFv/36UDxTzpbM/fXWgxh7iZpiFJ/GcGOLaG63QGjvDvCBiJlgc/U+YAjpWw7NzuT33muKWltbI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=KDN4f0P3; 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="KDN4f0P3" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5686A1F0089C; Wed, 16 Sep 2026 10:36:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789555008; bh=QswVIK5fqm1TPZvdvY47hhGDI5tFO0R6YYtxVOJiBPY=; h=From:To:Cc:Subject:Date:Reply-To; b=KDN4f0P33Hhwm7VGo6UvQWZxHIjOPbGlYFd94lHxYpHoA/a/NPY7iFcAGXfs/fxo3 oaHAkO0fraQZO/FPDeX2t7wOXJyBt0J9TRmPl0O6A8/NLFeP1p5AeHnPypuZLuCjWL ajgf5RuqGQBEK+KHiopjmLcpxJM9gNeMgzVmBgao= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89875: media: ti: vpe: quiesce overflow recovery before freeing streams Date: Wed, 16 Sep 2026 11:30:05 +0100 Message-ID: <2026091628-CVE-2026-89875-bbdb@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=3739; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=+BJaSRIgp7+0EVHQpvTigB/F76+zLG1FdhqpMAR80PM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmr8juWXT4jmrHv+WOH+5/S6pZbB5jYuwUfXJ+30v/75 66YzpLAjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjI6UKG+eVTZS6IXPmWs9kp fv5JXdZ7p/bX7GNYMFe4uXqdzZbiO8m3N5R8+zl3s0TBdwA= 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: ti: vpe: quiesce overflow recovery before freeing streams The VIP overflow recovery worker is armed from the hardirq handler when a FIFO overflow is detected, and the list-complete path looks the stream up through the VPDMA list private pointer. Both keep touching stream, port and device state; the recovery worker also resets the parser and VPDMA, repopulates the descriptor list, and re-enables the per-list IRQs. vip_stop_streaming() masks and clears the per-list IRQs, but it neither synchronizes the hardirq handler nor disables recovery_work. An overflow IRQ that has already queued recovery_work, or a list-complete IRQ in flight when the stream is torn down, can therefore still dereference the stream after its resources are released: the descriptor list is freed by vip_release_stream() on file release, and the stream itself by free_stream() on unbind/remove. Drain the recovery worker and the IRQ handler at both teardown points through a shared vip_quiesce_stream() helper, before any stream-owned resource is released. disable_work_sync() cancels pending recovery_work, drains a running instance, and raises its disable depth, so a subsequent schedule_work() issued by a racing IRQ handler is rejected at the workqueue scheduler: recovery_work cannot be requeued after disable_work_sync() takes effect. The worker may still re-enable the per-list IRQs before disable_work_sync() returns; disable_irqs() then masks those sources and synchronize_irq() waits for any in-flight handler that still dereferences stream state. In vip_stop_streaming() the helper runs before the parser is stopped, since a worker drained by disable_work_sync() may re-enable the parser before exiting and would otherwise undo the stop. recovery_work is created disabled and enabled in vip_start_streaming() before IRQs, pairing the enable with the teardown disable across the streaming lifecycle. This issue was found by an in-house static analysis tool and confirmed by manual code review. The Linux kernel CVE team has assigned CVE-2026-89875 to this issue. Affected and fixed versions =========================== Issue introduced in 7.0 with commit fc2873aa4a21355593b55eb49ff534d31f81c584 and fixed in 7.2.5 with commit fd5b4a14c87b21e1c9eaee603b01bb7fa7db45c8 Issue introduced in 7.0 with commit fc2873aa4a21355593b55eb49ff534d31f81c584 and fixed in 7.3-rc1 with commit aeaacc3001449d44b4ab7da56331121d1f3b137b 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-89875 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/ti/vpe/vip.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/fd5b4a14c87b21e1c9eaee603b01bb7fa7db45c8 https://git.kernel.org/stable/c/aeaacc3001449d44b4ab7da56331121d1f3b137b