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

Medium 5.5 Published Updated

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

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

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 include 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.

All Linux kernel vulnerabilities

Sources

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 and 4 more.

Is CVE-2025-37877 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free