First published: Fri May 09 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-37877 has a high severity rating due to potential disruptions in the IOMMU functionality.
To fix CVE-2025-37877, update to the latest stable version of the Linux kernel that addresses this vulnerability.
Users running affected versions of the Linux kernel with IOMMU-enabled hardware are vulnerable to CVE-2025-37877.
CVE-2025-37877 addresses issues related to improper management of IOMMU device registrations and group cleanups.
CVE-2025-37877 is classified under 'kernel vulnerabilities' specifically impacting IOMMU operations.