CVE-2026-43352
Race Condition in Linux Kernel I3C MIPI-HCI Driver
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's i3c driver, specifically in the mipi-i3c-hci component responsible for handling DMA ring abort operations.
The issue arises because the abort logic for the DMA ring has several flaws: it issues an abort even if the ring is already stopped, does not properly re-initialize the completion used to wait for abort completion, unintentionally clears a control bit (RING_CTRL_ENABLE) that resets hardware ring pointers and disrupts the controller state, and does not treat an already stopped ring as a successful abort condition.
The fix involves checking if the ring is running before aborting, re-initializing the completion when needed, ensuring the control bit remains asserted during abort, and treating an already stopped ring as a successful abort.
How can this vulnerability impact me? :
This vulnerability can cause improper handling of the DMA ring abort process in the i3c driver, potentially leading to disruption of the controller state.
Specifically, the unintended clearing of control bits and incorrect abort handling may reset hardware ring pointers unexpectedly, which could result in instability or malfunction of the hardware controller relying on this driver.
Such disruptions could affect system reliability or performance where this driver and hardware are in use.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability involves incorrect handling of the DMA ring abort sequence in the Linux kernel's i3c mipi-i3c-hci driver.
To mitigate this vulnerability, you should update your Linux kernel to a version that includes the fix for this issue. The fix corrects 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.
- Treating an already stopped ring as a successful condition.
Applying the kernel update will prevent the flawed abort logic from disrupting the controller state.