iommu/msm: Unwind probe state on registration failure
CVE-2026-89452 · published 11 Sept 2026
How serious is it
- Severity: high, CVSS score 8.4 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-89452?
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: 42df43b36163ed7d0ab13992e411093252903273 to < 6a1ae472113762f794682229a0f233f1ee0f69a4, 42df43b36163ed7d0ab13992e411093252903273 to < 51e37f9179387b6e3fa64a3d3b4fece1a38b3a02, 42df43b36163ed7d0ab13992e411093252903273 to < f532401be9312ecd166f616bb74a65b0b4c150fa, 42df43b36163ed7d0ab13992e411093252903273 to < 7f7074a886c4a93e3d12076ce60a510a1ebe400c
- Linux Linux: 4.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:
iommu/msm: Unwind probe state on registration failure
msm_iommu_probe() adds its devm-managed IOMMU object to
qcom_iommu_devices before adding the IOMMU sysfs device and registering
it with the IOMMU core.
If iommu_device_sysfs_add() fails, probe returns with the object still on
qcom_iommu_devices. The driver core then releases the devm allocation,
leaving a dangling list entry that later list walks may dereference.
If iommu_device_register() fails, the same dangling list entry remains
and the sysfs device is left registered as well.
Unwind the sysfs device and global list entry in reverse setup order on
the corresponding failure paths.
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/6a1ae472113762f794682229a0f233f1ee0f69a4
- git.kernel.org/stable/c/51e37f9179387b6e3fa64a3d3b4fece1a38b3a02
- git.kernel.org/stable/c/f532401be9312ecd166f616bb74a65b0b4c150fa
- git.kernel.org/stable/c/7f7074a886c4a93e3d12076ce60a510a1ebe400c
- git.kernel.org/stable/c/535a200220ca2c83bc8bf54bd2cbe045d6ee70c4
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON