CVE-2025-37877

{"id": "CVE-2025-37877", "cveTags": [], "metrics": {}, "published": "2025-05-09T07:16:08.907", "references": [{"url": "https://git.kernel.org/stable/c/104a84276821aed0ed241ce0d82d6c3267e3fcb8", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/280e5a30100578106a4305ce0118e0aa9b866f12", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/b14d98641312d972bb3f38e82eddf92898522389", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Clear iommu-dma ops on cleanup\n\nIf iommu_device_register() encounters an error, it can end up tearing\ndown already-configured groups and default domains, however this\ncurrently still leaves devices hooked up to iommu-dma (and even\nhistorically the behaviour in this area was at best inconsistent across\narchitectures/drivers...) Although in the case that an IOMMU is present\nwhose driver has failed to probe, users cannot necessarily expect DMA to\nwork anyway, it's still arguable that we should do our best to put\nthings back as if the IOMMU driver was never there at all, and certainly\nthe potential for crashing in iommu-dma itself is undesirable. Make sure\nwe clean up the dev->dma_iommu flag along with everything else."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: iommu: Clear iommu-dma ops on cleanup Si iommu_device_register() encuentra un error, puede terminar derribando grupos ya configurados y dominios predeterminados, sin embargo, esto actualmente todav\u00eda deja dispositivos conectados a iommu-dma (e incluso hist\u00f3ricamente el comportamiento en esta \u00e1rea era, en el mejor de los casos, inconsistente entre arquitecturas/controladores...) Aunque en el caso de que haya un IOMMU cuyo controlador no haya podido sondear, los usuarios no necesariamente pueden esperar que DMA funcione de todos modos, todav\u00eda se puede argumentar que deber\u00edamos hacer todo lo posible para volver a poner las cosas como si el controlador IOMMU nunca hubiera estado all\u00ed, y ciertamente el potencial de bloqueo en iommu-dma en s\u00ed mismo es indeseable. Aseg\u00farese de limpiar el indicador dev->dma_iommu junto con todo lo dem\u00e1s."}], "lastModified": "2025-05-12T17:32:32.760", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}