Answer in brief
CVE-2025-37877 records a Medium severity (CVSS 5.5) vulnerability in iommu: Clear iommu-dma ops on cleanup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b5c58b2fdc427e7958412ecb2de2804a1f7c1572 <b14d98641312d972bb3f38e82eddf92898522389 || >=b5c58b2fdc427e7958412ecb2de2804a1f7c1572 <104a84276821aed0ed241ce0d82d6c3267e3fcb8 || >=b5c58b2fdc427e7958412ecb2de2804a1f7c1572 <280e5a30100578106a4305ce0118e0aa9b866f12 | b14d98641312d972bb3f38e82eddf92898522389, 104a84276821aed0ed241ce0d82d6c3267e3fcb8, 280e5a30100578106a4305ce0118e0aa9b866f12 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
May 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.