In the Linux kernel, the following vulnerability has been resolved: iommu/msm: Unwind probe state on registration failure msm_iommu_probe() adds its… (CVE-2026-89452)
A vulnerability in the Linux kernel's msm_iommu_probe() function can lead to dangling list entries if certain registration steps fail. Specifically, failures in iommu_device_sysfs_add() or iommu_device_register() leave inconsistent states that may cause later list traversals to dereference invalid pointers. The issue is addressed by properly unwinding the sysfs device and global list entries on failure paths.
AI Analysis
Technical Summary
The Linux kernel vulnerability involves the msm_iommu_probe() function in the iommu/msm driver. When registration of the IOMMU sysfs device fails, the function returns without removing the devm-managed IOMMU object from the global qcom_iommu_devices list. This results in a dangling list entry after the driver core releases the devm allocation. Similarly, if iommu_device_register() fails, the dangling list entry remains and the sysfs device remains registered. The fix involves unwinding the sysfs device and global list entries in reverse order on failure to prevent invalid list dereferences.
Potential Impact
The vulnerability can cause the kernel to have dangling pointers in its internal device lists, potentially leading to kernel instability or crashes when these lists are later traversed. No direct exploitation details or impact on confidentiality, integrity, or availability are provided.
Mitigation Recommendations
A fix has been implemented to properly unwind and clean up the sysfs device and global list entries on failure paths in msm_iommu_probe(). Users should apply the updated Linux kernel version containing this fix once available. Patch status is not explicitly confirmed; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: iommu/msm: Unwind probe state on registration failure msm_iommu_probe() adds its… (CVE-2026-89452)
Description
A vulnerability in the Linux kernel's msm_iommu_probe() function can lead to dangling list entries if certain registration steps fail. Specifically, failures in iommu_device_sysfs_add() or iommu_device_register() leave inconsistent states that may cause later list traversals to dereference invalid pointers. The issue is addressed by properly unwinding the sysfs device and global list entries on failure paths.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability involves the msm_iommu_probe() function in the iommu/msm driver. When registration of the IOMMU sysfs device fails, the function returns without removing the devm-managed IOMMU object from the global qcom_iommu_devices list. This results in a dangling list entry after the driver core releases the devm allocation. Similarly, if iommu_device_register() fails, the dangling list entry remains and the sysfs device remains registered. The fix involves unwinding the sysfs device and global list entries in reverse order on failure to prevent invalid list dereferences.
Potential Impact
The vulnerability can cause the kernel to have dangling pointers in its internal device lists, potentially leading to kernel instability or crashes when these lists are later traversed. No direct exploitation details or impact on confidentiality, integrity, or availability are provided.
Mitigation Recommendations
A fix has been implemented to properly unwind and clean up the sysfs device and global list entries on failure paths in msm_iommu_probe(). Users should apply the updated Linux kernel version containing this fix once available. Patch status is not explicitly confirmed; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-g6rr-fv4f-cc2j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89452"]
Threat ID: 6aa4a02355bf5e2cf5a869ad
Added to database: 09/12/2026, 00:43:15 UTC
Last enriched: 09/12/2026, 01:17:15 UTC
Last updated: 09/12/2026, 01:17:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.