What’s Vulnerable › Vulnerabilities
CVE-2026-43352: i3c: mipi-i3c-hci: Correct RING_CTRL_ABORT handling in DMA dequeue
- Severity: high (CVSS 7.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-05-08 · updated 2026-10-30
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.
Affected products
- Linux kernel: from 5.11 before 6.18.19; from 6.19 before 6.19.9; 7.0-rc1, 7.0-rc2, 7.0-rc3 — fixed in 6.18.19, 6.19.9
- Linux: 5.11 — fixed in 7.0
How to fix
Upgrade to a fixed version: Linux kernel 6.18.19, 6.19.9; Linux 7.0. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/003df94bcc9227e8e930abd03ac7f63ac10033dc
- https://git.kernel.org/stable/c/04b2853fdbb2ec9d03ece45da3c830396647120f
- https://git.kernel.org/stable/c/377e75da122ffce7cec551f43fa884d57f2f8e63
- https://git.kernel.org/stable/c/5549611888f5ca2db5e8e692b57f30626ddf9898
- https://git.kernel.org/stable/c/55a0b47a372245f7667e0a4ba5c6f2a4c7a889a6
- https://git.kernel.org/stable/c/b795e68bf3073d67bebbb5a44d93f49efc5b8cc7
Get alerted when CVE-2026-43352 or the next vulnerability affects your stack