i3c: mipi-i3c-hci: Correct RING_CTRL_ABORT handling in DMA dequeue
CVE-2026-43352 · published 8 May 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-43352?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 9ad9a52cce2828d932ae9495181e3d6414f72c07 to < 04b2853fdbb2ec9d03ece45da3c830396647120f, 9ad9a52cce2828d932ae9495181e3d6414f72c07 to < 55a0b47a372245f7667e0a4ba5c6f2a4c7a889a6, 9ad9a52cce2828d932ae9495181e3d6414f72c07 to < 003df94bcc9227e8e930abd03ac7f63ac10033dc, 9ad9a52cce2828d932ae9495181e3d6414f72c07 to < 5549611888f5ca2db5e8e692b57f30626ddf9898
- Linux Linux: 5.11
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/04b2853fdbb2ec9d03ece45da3c830396647120f
- git.kernel.org/stable/c/55a0b47a372245f7667e0a4ba5c6f2a4c7a889a6
- git.kernel.org/stable/c/003df94bcc9227e8e930abd03ac7f63ac10033dc
- git.kernel.org/stable/c/5549611888f5ca2db5e8e692b57f30626ddf9898
- git.kernel.org/stable/c/b795e68bf3073d67bebbb5a44d93f49efc5b8cc7
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON