<?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 15:58:55 +0000</lastBuildDate>
    <item>
      <title>bdu:2020-01475</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2020-01475</link>
      <description>bdu:2020-01475</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2020-01475</guid>
    </item>
    <item>
      <title>certfr-2019-avi-541 — De multiples vulnérabilités ont été découvertes dans Xen . Elles
permettent à un attaquant de provoquer un déni de serv…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2019-avi-541</link>
      <description>certfr-2019-avi-541</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2019-avi-541</guid>
    </item>
    <item>
      <title>cnvd-2019-40061</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2019-40061</link>
      <description>cnvd-2019-40061</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2019-40061</guid>
    </item>
    <item>
      <title>EUVD-2026-58715</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-58715</link>
      <description>EUVD-2026-58715</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-58715</guid>
    </item>
    <item>
      <title>fkie_cve-2019-18424</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2019-18424</link>
      <description>&lt;p&gt;An issue was discovered in Xen through 4.12.x allowing attackers to gain host OS privileges via DMA in a situation where an untrusted domain has access to a physical device. This occurs because passed through PCI devices may corrupt host memory after deassignment. When a PCI device is assigned to an untrusted domain, it is possible for that domain to program the device to DMA to an arbitrary address. The IOMMU is used to protect the host from malicious DMA by making sure that the device addresses can only target memory assigned to the guest. However, when the guest domain is torn down, or the device is deassigned, the device is assigned back to dom0, thus allowing any in-flight DMA to potentially target critical host data. An untrusted domain with access to a physical device can DMA into host memory, leading to privilege escalation. Only systems where guests are given direct access to physical devices capable of DMA (PCI pass-through) are vulnerable. Systems which do not use PCI pass-through are not vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in Xen through 4.12.x allowing attackers to gain host OS privileges via DMA in a situation where an untrusted domain has access to a physical device. This occurs because passed through PCI devices may corrupt host memory after deassignment. When a PCI device is assigned to an untrusted domain, it is possible for that domain to program the device to DMA to an arbitrary address. The IOMMU is used to protect the host from malicious DMA by making sure that the device addresses can only target memory assigned to the guest. However, when the guest domain is torn down, or the device is deassigned, the device is assigned back to dom0, thus allowing any in-flight DMA to potentially target critical host data. An untrusted domain with access to a physical device can DMA into host memory, leading to privilege escalation. Only systems where guests are given direct access to physical devices capable of DMA (PCI pass-through) are vulnerable. Systems which do not use PCI pass-through are not vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2019-18424</guid>
    </item>
    <item>
      <title>GHSA-3q68-jh6h-39cm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3q68-jh6h-39cm</link>
      <description>&lt;p&gt;An issue was discovered in Xen through 4.12.x allowing attackers to gain host OS privileges via DMA in a situation where an untrusted domain has access to a physical device. This occurs because passed through PCI devices may corrupt host memory after deassignment. When a PCI device is assigned to an untrusted domain, it is possible for that domain to program the device to DMA to an arbitrary address. The IOMMU is used to protect the host from malicious DMA by making sure that the device addresses can only target memory assigned to the guest. However, when the guest domain is torn down, or the device is deassigned, the device is assigned back to dom0, thus allowing any in-flight DMA to potentially target critical host data. An untrusted domain with access to a physical device can DMA into host memory, leading to privilege escalation. Only systems where guests are given direct access to physical devices capable of DMA (PCI pass-through) are vulnerable. Systems which do not use PCI pass-through are not vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in Xen through 4.12.x allowing attackers to gain host OS privileges via DMA in a situation where an untrusted domain has access to a physical device. This occurs because passed through PCI devices may corrupt host memory after deassignment. When a PCI device is assigned to an untrusted domain, it is possible for that domain to program the device to DMA to an arbitrary address. The IOMMU is used to protect the host from malicious DMA by making sure that the device addresses can only target memory assigned to the guest. However, when the guest domain is torn down, or the device is deassigned, the device is assigned back to dom0, thus allowing any in-flight DMA to potentially target critical host data. An untrusted domain with access to a physical device can DMA into host memory, leading to privilege escalation. Only systems where guests are given direct access to physical devices capable of DMA (PCI pass-through) are vulnerable. Systems which do not use PCI pass-through are not vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3q68-jh6h-39cm</guid>
    </item>
    <item>
      <title>gsd-2019-18424</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2019-18424</link>
      <description>gsd-2019-18424</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2019-18424</guid>
    </item>
    <item>
      <title>openSUSE-SU-2019:2506-1 — Security update for xen</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2019:2506-1</link>
      <description>&lt;p&gt;Security update for xen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for xen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2019:2506-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2019:2960-1 — Security update for xen</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2019:2960-1</link>
      <description>&lt;p&gt;Security update for xen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for xen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2019:2960-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2019-18424</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-18424</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen&lt;/p&gt;
&lt;p&gt;An issue was discovered in Xen through 4.12.x allowing attackers to gain host OS privileges via DMA in a situation where an untrusted domain has access to a physical device. This occurs because passed through PCI devices may corrupt host memory after deassignment. When a PCI device is assigned to an untrusted domain, it is possible for that domain to program the device to DMA to an arbitrary address. The IOMMU is used to protect the host from malicious DMA by making sure that the device addresses can only target memory assigned to the guest. However, when the guest domain is torn down, or the device is deassigned, the device is assigned back to dom0, thus allowing any in-flight DMA to potentially target critical host data. An untrusted domain with access to a physical device can DMA into host memory, leading to privilege escalation. Only systems where guests are given direct access to physical devices capable of DMA (PCI pass-through) are vulnerable. Systems which do not use PCI pass-through are not vulnerable.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen&lt;/p&gt;
&lt;p&gt;An issue was discovered in Xen through 4.12.x allowing attackers to gain host OS privileges via DMA in a situation where an untrusted domain has access to a physical device. This occurs because passed through PCI devices may corrupt host memory after deassignment. When a PCI device is assigned to an untrusted domain, it is possible for that domain to program the device to DMA to an arbitrary address. The IOMMU is used to protect the host from malicious DMA by making sure that the device addresses can only target memory assigned to the guest. However, when the guest domain is torn down, or the device is deassigned, the device is assigned back to dom0, thus allowing any in-flight DMA to potentially target critical host data. An untrusted domain with access to a physical device can DMA into host memory, leading to privilege escalation. Only systems where guests are given direct access to physical devices capable of DMA (PCI pass-through) are vulnerable. Systems which do not use PCI pass-through are not vulnerable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-18424</guid>
    </item>
  </channel>
</rss>
