iommu/msm: Unwind probe state on registration failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 42df43b36163ed7d0ab13992e411093252903273 · fixed in 6a1ae472113762f794682229a0f233f1ee0f69a4; From 42df43b36163ed7d0ab13992e411093252903273 · fixed in 51e37f9179387b6e3fa64a3d3b4fece1a38b3a02; From 42df43b36163ed7d0ab13992e411093252903273 · fixed in f532401be9312ecd166f616bb74a65b0b4c150fa; From 42df43b36163ed7d0ab13992e411093252903273 · fixed in 7f7074a886c4a93e3d12076ce60a510a1ebe400c; From 42df43b36163ed7d0ab13992e411093252903273 · fixed in 535a200220ca2c83bc8bf54bd2cbe045d6ee70c4
- Linux Linux
4.11
- KernelLinux
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