# CVE-2026-93205: iommu/arm-smmu-v3: Manage teardown with devm

> A use-after-free vulnerability in the Linux kernel ARM SMMUv3 driver allows local attackers to cause denial of service or execute arbitrary code due to incorrect resource teardown order.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-103688, BELL-CVE-2026-93205, DEBIAN-CVE-2026-93205, GHSA-7g45-qp7m-q8xg, UBUNTU-CVE-2026-93205

## What is CVE-2026-93205?

CVE-2026-93205 is an use after free vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93205?


## How do I fix CVE-2026-93205?

Apply the vendor's patch.

## Is CVE-2026-93205 being exploited?

There is no known exploitation of CVE-2026-93205 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93205 and fix it if it is affected.

What it is: CVE-2026-93205 is an use after free vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93205 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93205/ (Markdown: https://insights.sbomify.com/CVE-2026-93205/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93205
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93205
- OSV: https://osv.dev/vulnerability/CVE-2026-93205

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93205/
Summaries are generated and may contain mistakes; the official description above is the record.