# CVE-2025-37877: iommu: Clear iommu-dma ops on cleanup

> A missing cleanup in the Linux kernel IOMMU driver can cause a crash when device registration fails, leading to denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-62621, AZL-70147, BELL-CVE-2025-37877, DEBIAN-CVE-2025-37877, GHSA-3v3m-75mh-5x2r, ROOT-OS-DEBIAN-11-CVE-2025-37877, ROOT-OS-DEBIAN-12-CVE-2025-37877, ROOT-OS-UBUNTU-2204-CVE-2025-37877, ROOT-OS-UBUNTU-2404-CVE-2025-37877, UBUNTU-CVE-2025-37877

## What is CVE-2025-37877?

CVE-2025-37877 is a medium-severity vulnerability in Linux kernel, published on 9 May 2025. 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: Clear iommu-dma ops on cleanup

If iommu_device_register() encounters an error, it can end up tearing
down already-configured groups and default domains, however this
currently still leaves devices hooked up to iommu-dma (and even
historically the behaviour in this area was at best inconsistent across
architectures/drivers...) Although in the case that an IOMMU is present
whose driver has failed to probe, users cannot necessarily expect DMA to
work anyway, it's still arguable that we should do our best to put
things back as if the IOMMU driver was never there at all, and certainly
the potential for crashing in iommu-dma itself is undesirable. Make sure
we clean up the dev->dma_iommu flag along with everything else.

## Which versions are affected by CVE-2025-37877?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-37877?

Apply the vendor's patch.

## Is CVE-2025-37877 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37877 and fix it if it is affected.

What it is: CVE-2025-37877 is a medium-severity vulnerability in Linux kernel, published on 9 May 2025. 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-2025-37877 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2025-37877/ (Markdown: https://insights.sbomify.com/CVE-2025-37877/index.md)
```

## Sources

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

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