iommu/arm-smmu-v3: Manage teardown with devm
- 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.109, 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/arm-smmu-v3: Manage teardown with devm arm_smmu_device_remove() manually frees the IOPF queue, destroys the vmid_map and disables the device, while the IRQs and queues are devm managed. devm unwinds only after remove() returns, so the cleanup runs in the wrong order. The IOPF queue is freed before the event-queue IRQ whose handler uses it. Manage all of it with devm so the unwind order is correct. Free the IOPF queue and vmid_map via devm actions, and disable the device from one registered after arm_smmu_device_reset(). This is also a prerequisite for fixing a Tegra241 CMDQV CMD_SYNC use-after-free in the subsequent patch.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 395ad89d11fd93f79a6b942e91fc409807a63c4b · fixed in 64b1a9384db9cabf1bde378a2d5c1923fd67ea0d; From 395ad89d11fd93f79a6b942e91fc409807a63c4b · fixed in 981686f4137760a16a03c5193f11d85133533f93; From 395ad89d11fd93f79a6b942e91fc409807a63c4b · fixed in 2235eafda9b3df9295efd0593cd4a8977440c3f6; From 395ad89d11fd93f79a6b942e91fc409807a63c4b · fixed in 78fd5a2d65f3546cb4285f8e52f445baecbd00e0; From 395ad89d11fd93f79a6b942e91fc409807a63c4b · fixed in 2bd22a0d40503a65d243b011de146603c8ce1cbc
- Linux Linux
5.14
- KernelLinux
From 5.14.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4