CVE-2026-43352 Details
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.
A vulnerability in the Linux kernel's MIPI I3C Host Controller Interface (HCI) driver has been addressed. The issue arose from improper handling of the RING_CTRL_ABORT command during Direct Memory Access (DMA) operations. Several flaws were identified: the driver would issue a ring abort command even if the ring had already stopped, the mechanism for waiting for the abort operation to complete was not properly re-initialized, the abort sequence inadvertently disabled the RING_CTRL_ENABLE signal which is crucial for maintaining the correct state of hardware ring pointers, and the abort operation did not recognize when the ring was already stopped, leading to unnecessary actions. The vulnerability has been fixed by implementing a check to ensure the ring is active before issuing an abort, re-initializing the completion signal when necessary, keeping the RING_CTRL_ENABLE signal active during the abort process, and acknowledging an already stopped ring as a successful abort condition.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/003df94bcc9227e8e930abd03ac7f63ac10033dc | kernel.org | Patch |
| https://git.kernel.org/stable/c/5549611888f5ca2db5e8e692b57f30626ddf9898 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b795e68bf3073d67bebbb5a44d93f49efc5b8cc7 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.11, < 6.18.19 >= 6.19, < 6.19.9 7.0 rc1 7.0 rc2 7.0 rc3 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 15, 2026 | Initial Analysis | [email protected] |
| May 11, 2026 | CVE Modified | kernel.org |
| May 8, 2026 | New CVE Received | kernel.org |