# iommu: Clear iommu-dma ops on cleanup

CVE record · `CVE-2025-37877`

- **Identifiers:** `CVE-2025-37877`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 9 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 9 May 2025, 06:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `b5c58b2fdc427e7958412ecb2de2804a1f7c1572 to before b14d98641312d972bb3f38e82eddf92898522389` (git)
  - affected: `b5c58b2fdc427e7958412ecb2de2804a1f7c1572 to before 104a84276821aed0ed241ce0d82d6c3267e3fcb8` (git)
  - affected: `b5c58b2fdc427e7958412ecb2de2804a1f7c1572 to before 280e5a30100578106a4305ce0118e0aa9b866f12` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.12`
  - unaffected: `before 6.12` (semver)
  - unaffected: `6.12.26 to 6.12.*, inclusive` (semver)
  - unaffected: `6.14.5 to 6.14.*, inclusive` (semver)
  - unaffected: `6.15 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel IOMMU code is affected from the 6.12 series until fixed in 6.12.26, 6.14.5, and 6.15. When IOMMU driver registration fails, devices can stay attached to the iommu-dma code after cleanup, which could crash the kernel. The source gives few details on what an attacker would need. Upgrade to 6.12.26, 6.14.5, 6.15, or a later release.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 9 May 2025, 06:45 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-37877)
- 9 May 2025, 07:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-37877)

## Sources

- [CVE List: CVE-2025-37877](https://www.cve.org/CVERecord?id=CVE-2025-37877)
- [NVD: CVE-2025-37877](https://nvd.nist.gov/vuln/detail/CVE-2025-37877)

### References from the CNA

- <https://git.kernel.org/stable/c/b14d98641312d972bb3f38e82eddf92898522389>
- <https://git.kernel.org/stable/c/104a84276821aed0ed241ce0d82d6c3267e3fcb8>
- <https://git.kernel.org/stable/c/280e5a30100578106a4305ce0118e0aa9b866f12>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-37877>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-37877/>. Everything for agents: <https://agentprime.io/llms.txt>.
