CVE-2025-37877

Source
https://nvd.nist.gov/vuln/detail/CVE-2025-37877
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-37877.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-37877
Downstream
Published
2025-05-09T07:16:08Z
Modified
2025-08-09T19:01:28Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

iommu: Clear iommu-dma ops on cleanup

If iommudeviceregister() 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.

References

Affected packages