CVE-2025-37877
Last modified
CVE-2025-37877 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | < 6.12.26 | — |
| Linux | Linux Kernel | >= 6.13, < 6.14.5 | — |
| Linux | Linux Kernel | 6.15 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-37877?
How severe is CVE-2025-37877?
How do I fix CVE-2025-37877?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-37871In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37872In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37873In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37874In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37875In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37876In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37878In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37879In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-3788A vulnerability was found in baseweb JSite 1.0. It has been …5.4
- CVE-2025-37880In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37881In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-37882In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-37877?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
