https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 16:42:31 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-01390 bdu:2026-01390 https://cve.radiocsirt.org/vuln/bdu:2026-01390 https://cve.radiocsirt.org/vuln/bell-cve-2025-37877 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-37877 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0559 certfr-2025-avi-0559 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0559 https://cve.radiocsirt.org/vuln/euvd-2026-314297 EUVD-2026-314297 https://cve.radiocsirt.org/vuln/euvd-2026-314297 https://cve.radiocsirt.org/vuln/fkie_cve-2025-37877 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Clear iommu-dma ops on cleanup</p> <p>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&#39;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-&gt;dma_iommu flag along with everything else.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Clear iommu-dma ops on cleanup</p> <p>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&#39;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-&gt;dma_iommu flag along with everything else.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-37877 https://cve.radiocsirt.org/vuln/ghsa-3v3m-75mh-5x2r <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Clear iommu-dma ops on cleanup</p> <p>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&#39;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-&gt;dma_iommu flag along with everything else.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu: Clear iommu-dma ops on cleanup</p> <p>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&#39;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-&gt;dma_iommu flag along with everything else.</p> https://cve.radiocsirt.org/vuln/ghsa-3v3m-75mh-5x2r https://cve.radiocsirt.org/vuln/msrc_cve-2025-37877 msrc_CVE-2025-37877 https://cve.radiocsirt.org/vuln/msrc_cve-2025-37877 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37877 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 210 more</p> <p>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&#39;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-&gt;dma_iommu flag along with everything else.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 210 more</p> <p>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&#39;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-&gt;dma_iommu flag along with everything else.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37877 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0991 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0991