CVE-2026-93205: Linux kernel · iommu/arm-smmu-v3: Manage teardown with devm
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 981686f4137760a16a03c5193f11d85133533f93 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 20:10 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 981686f4137760a16a03c5193f11d85133533f93, 2235eafda9b3df9295efd0593cd4a8977440c3f6, 78fd5a2d65f3546cb4285f8e52f445baecbd00e0 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available that manages all teardown resources with devm to ensure correct cleanup order. Users should update to the patched Linux kernel versions containing the commits identified by the fixedVersions hashes. No additional mitigation is required beyond applying the official fix.
Description
A vulnerability in the Linux kernel's ARM SMMU v3 driver involves improper management of resource teardown order. The arm_smmu_device_remove() function manually frees the IOPF queue and destroys the vmid_map before devm-managed IRQs and queues are unwound, causing cleanup to occur in the wrong order. This can lead to use-after-free conditions. The issue is fixed by managing all resources with devm to ensure correct unwind order.
References
- git.kernel.org/stable/c/64b1a9384db9cabf1bde378a2d5c1923fd67ea0d (opens in a new tab)
- git.kernel.org/stable/c/981686f4137760a16a03c5193f11d85133533f93 (opens in a new tab)
- git.kernel.org/stable/c/2235eafda9b3df9295efd0593cd4a8977440c3f6 (opens in a new tab)
- git.kernel.org/stable/c/78fd5a2d65f3546cb4285f8e52f445baecbd00e0 (opens in a new tab)
- git.kernel.org/stable/c/2bd22a0d40503a65d243b011de146603c8ce1cbc (opens in a new tab)