From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 B71EF3ED123 for ; Fri, 8 May 2026 14:22:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250135; cv=none; b=nBTW8dfrGnUD16XAOuBQUb7XNzpsSNA6gWqP1+iP+HtGXsrWYEDPHx1WurcXd8LSonLOhj+vtDFXjBRlGOJzKCIy0qmjXJ7h6rJx77FR/XE/iDxKhqfRXtgWUub59xyRrS6ngz17PfrEE636wXa32Cut264WFnMrlVcNcyWdqdA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778250135; c=relaxed/simple; bh=KddmCt05B7rTu9bregCotwBb6XJhhpybB32Z2nq7MhU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=hTUT/7BsvhQj5AOZ25+nW45X0vmb54BA470Tv920SwrEv4wj/Thb2PLpPnbVv4fTpWseEGVvyPKJEXvgRtoET7eM0nCrdpdYi2XlEIMKibeRrey4VrQCKfw075v8NRQz7ZNzj6qptBRUsI/lKy+rteWsWIiD91tkJ9VDNbpBwYU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=k7VaLY+q; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="k7VaLY+q" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 12193C2BCB0; Fri, 8 May 2026 14:22:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778250135; bh=KddmCt05B7rTu9bregCotwBb6XJhhpybB32Z2nq7MhU=; h=From:To:Cc:Subject:Date:Reply-To:From; b=k7VaLY+qV+G2gNzmZP6UPjOMCLJ2yK+J6pSJAALKciMfQPU5SXvc4KXssuLeYfG2Z 6Ibfhe1/dCuJUzGCScoyllLBnkAtpjbNRPYjVTWCpSUKC+RxZbuqfk29AMgBnuv2f0 fk9p2yiTaFxnNcS5x1Mi3EA7KBVKq9M1e4c0eudM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43352: i3c: mipi-i3c-hci: Correct RING_CTRL_ABORT handling in DMA dequeue Date: Fri, 8 May 2026 16:21:21 +0200 Message-ID: <2026050823-CVE-2026-43352-73ed@gregkh> X-Mailer: git-send-email 2.54.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=2830; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=kuExPUwE3mytBV9pirUkqCD69QCx9se5F2ZS8W3+zWs=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/PyYLbqo//tTt8Z9FOds4I14tzQyp32K5ouGY2VQvT ZEdT+eZdMSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBE2NwZ5ideTfF3ZIy3FZGv ufRXqrdHijfrGsM8+yN7e6XEUqcWhEzve1NXLbNTPsUbAA== 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: i3c: mipi-i3c-hci: Correct RING_CTRL_ABORT handling in DMA dequeue The logic used to abort the DMA ring contains several flaws: 1. The driver unconditionally issues a ring abort even when the ring has already stopped. 2. The completion used to wait for abort completion is never re-initialized, resulting in incorrect wait behavior. 3. The abort sequence unintentionally clears RING_CTRL_ENABLE, which resets hardware ring pointers and disrupts the controller state. 4. If the ring is already stopped, the abort operation should be considered successful without attempting further action. Fix the abort handling by checking whether the ring is running before issuing an abort, re-initializing the completion when needed, ensuring that RING_CTRL_ENABLE remains asserted during abort, and treating an already stopped ring as a successful condition. The Linux kernel CVE team has assigned CVE-2026-43352 to this issue. Affected and fixed versions =========================== Issue introduced in 5.11 with commit 9ad9a52cce2828d932ae9495181e3d6414f72c07 and fixed in 6.18.19 with commit 003df94bcc9227e8e930abd03ac7f63ac10033dc Issue introduced in 5.11 with commit 9ad9a52cce2828d932ae9495181e3d6414f72c07 and fixed in 6.19.9 with commit 5549611888f5ca2db5e8e692b57f30626ddf9898 Issue introduced in 5.11 with commit 9ad9a52cce2828d932ae9495181e3d6414f72c07 and fixed in 7.0 with commit b795e68bf3073d67bebbb5a44d93f49efc5b8cc7 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-43352 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/i3c/master/mipi-i3c-hci/dma.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/003df94bcc9227e8e930abd03ac7f63ac10033dc https://git.kernel.org/stable/c/5549611888f5ca2db5e8e692b57f30626ddf9898 https://git.kernel.org/stable/c/b795e68bf3073d67bebbb5a44d93f49efc5b8cc7