<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 17:24:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07407</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07407</link>
      <description>bdu:2025-07407</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07407</guid>
    </item>
    <item>
      <title>EUVD-2026-309562</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309562</link>
      <description>EUVD-2026-309562</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309562</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47140</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47140</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/amd: Clear DMA ops when switching domain&lt;/p&gt;
&lt;p&gt;Since commit 08a27c1c3ecf (&amp;#34;iommu: Add support to change default domain
of an iommu group&amp;#34;) a user can switch a device between IOMMU and direct
DMA through sysfs. This doesn&amp;#39;t work for AMD IOMMU at the moment because
dev-&amp;gt;dma_ops is not cleared when switching from a DMA to an identity
IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an
identity domain, causing an oops:&lt;/p&gt;
&lt;p&gt;# echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/unbind
  # echo identity &amp;gt; /sys/bus/pci/devices/0000:00:05.0/iommu_group/type
  # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/bind
   ...
  BUG: kernel NULL pointer dereference, address: 0000000000000028
   ...
   Call Trace:
    iommu_dma_alloc
    e1000e_setup_tx_resources
    e1000e_open&lt;/p&gt;
&lt;p&gt;Since iommu_change_dev_def_domain() calls probe_finalize() again, clear
the dma_ops there like Vt-d does.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/amd: Clear DMA ops when switching domain&lt;/p&gt;
&lt;p&gt;Since commit 08a27c1c3ecf (&amp;#34;iommu: Add support to change default domain
of an iommu group&amp;#34;) a user can switch a device between IOMMU and direct
DMA through sysfs. This doesn&amp;#39;t work for AMD IOMMU at the moment because
dev-&amp;gt;dma_ops is not cleared when switching from a DMA to an identity
IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an
identity domain, causing an oops:&lt;/p&gt;
&lt;p&gt;# echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/unbind
  # echo identity &amp;gt; /sys/bus/pci/devices/0000:00:05.0/iommu_group/type
  # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/bind
   ...
  BUG: kernel NULL pointer dereference, address: 0000000000000028
   ...
   Call Trace:
    iommu_dma_alloc
    e1000e_setup_tx_resources
    e1000e_open&lt;/p&gt;
&lt;p&gt;Since iommu_change_dev_def_domain() calls probe_finalize() again, clear
the dma_ops there like Vt-d does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47140</guid>
    </item>
    <item>
      <title>GHSA-vr5f-v75p-g4qw</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vr5f-v75p-g4qw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/amd: Clear DMA ops when switching domain&lt;/p&gt;
&lt;p&gt;Since commit 08a27c1c3ecf (&amp;#34;iommu: Add support to change default domain
of an iommu group&amp;#34;) a user can switch a device between IOMMU and direct
DMA through sysfs. This doesn&amp;#39;t work for AMD IOMMU at the moment because
dev-&amp;gt;dma_ops is not cleared when switching from a DMA to an identity
IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an
identity domain, causing an oops:&lt;/p&gt;
&lt;p&gt;# echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/unbind
  # echo identity &amp;gt; /sys/bus/pci/devices/0000:00:05.0/iommu_group/type
  # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/bind
   ...
  BUG: kernel NULL pointer dereference, address: 0000000000000028
   ...
   Call Trace:
    iommu_dma_alloc
    e1000e_setup_tx_resources
    e1000e_open&lt;/p&gt;
&lt;p&gt;Since iommu_change_dev_def_domain() calls probe_finalize() again, clear
the dma_ops there like Vt-d does.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/amd: Clear DMA ops when switching domain&lt;/p&gt;
&lt;p&gt;Since commit 08a27c1c3ecf (&amp;#34;iommu: Add support to change default domain
of an iommu group&amp;#34;) a user can switch a device between IOMMU and direct
DMA through sysfs. This doesn&amp;#39;t work for AMD IOMMU at the moment because
dev-&amp;gt;dma_ops is not cleared when switching from a DMA to an identity
IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an
identity domain, causing an oops:&lt;/p&gt;
&lt;p&gt;# echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/unbind
  # echo identity &amp;gt; /sys/bus/pci/devices/0000:00:05.0/iommu_group/type
  # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/bind
   ...
  BUG: kernel NULL pointer dereference, address: 0000000000000028
   ...
   Call Trace:
    iommu_dma_alloc
    e1000e_setup_tx_resources
    e1000e_open&lt;/p&gt;
&lt;p&gt;Since iommu_change_dev_def_domain() calls probe_finalize() again, clear
the dma_ops there like Vt-d does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vr5f-v75p-g4qw</guid>
    </item>
    <item>
      <title>gsd-2021-47140</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47140</link>
      <description>gsd-2021-47140</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47140</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47140</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47140</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Clear DMA ops when switching domain Since commit 08a27c1c3ecf (&amp;#34;iommu: Add support to change default domain of an iommu group&amp;#34;) a user can switch a device between IOMMU and direct DMA through sysfs. This doesn&amp;#39;t work for AMD IOMMU at the moment because dev-&amp;gt;dma_ops is not cleared when switching from a DMA to an identity IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an identity domain, causing an oops:   # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/unbind   # echo identity &amp;gt; /sys/bus/pci/devices/0000:00:05.0/iommu_group/type   # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/bind    ...   BUG: kernel NULL pointer dereference, address: 0000000000000028    ...    Call Trace:     iommu_dma_alloc     e1000e_setup_tx_resources     e1000e_open Since iommu_change_dev_def_domain() calls probe_finalize() again, clear the dma_ops there like Vt-d does.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Clear DMA ops when switching domain Since commit 08a27c1c3ecf (&amp;#34;iommu: Add support to change default domain of an iommu group&amp;#34;) a user can switch a device between IOMMU and direct DMA through sysfs. This doesn&amp;#39;t work for AMD IOMMU at the moment because dev-&amp;gt;dma_ops is not cleared when switching from a DMA to an identity IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an identity domain, causing an oops:   # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/unbind   # echo identity &amp;gt; /sys/bus/pci/devices/0000:00:05.0/iommu_group/type   # echo 0000:00:05.0 &amp;gt; /sys/sys/bus/pci/drivers/e1000e/bind    ...   BUG: kernel NULL pointer dereference, address: 0000000000000028    ...    Call Trace:     iommu_dma_alloc     e1000e_setup_tx_resources     e1000e_open Since iommu_change_dev_def_domain() calls probe_finalize() again, clear the dma_ops there like Vt-d does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47140</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0699 — Linux-Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0699</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0699</guid>
    </item>
  </channel>
</rss>
