<?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 02:45:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03590</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03590</link>
      <description>bdu:2024-03590</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03590</guid>
    </item>
    <item>
      <title>certfr-2022-avi-974 — De multiples vulnérabilités ont été découvertes dans Xen. Certaines
d'entre elles permettent à un attaquant de provoque…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2022-avi-974</link>
      <description>certfr-2022-avi-974</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2022-avi-974</guid>
    </item>
    <item>
      <title>EUVD-2026-202828</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-202828</link>
      <description>EUVD-2026-202828</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-202828</guid>
    </item>
    <item>
      <title>fkie_cve-2022-42320</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-42320</link>
      <description>&lt;p&gt;Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-42320</guid>
    </item>
    <item>
      <title>GHSA-p263-3p34-m82m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p263-3p34-m82m</link>
      <description>&lt;p&gt;Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p263-3p34-m82m</guid>
    </item>
    <item>
      <title>gsd-2022-42320</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-42320</link>
      <description>gsd-2022-42320</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-42320</guid>
    </item>
    <item>
      <title>SUSE-SU-2022:3925-1 — Security update for xen</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2022:3925-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-2022:3925-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-42320</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42320</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: xen, Ubuntu:18.04:LTS: xen, Ubuntu:20.04:LTS: xen, Ubuntu:22.04:LTS: xen, Ubuntu:24.04:LTS: xen, Ubuntu:25.10: xen, Ubuntu:26.04:LTS: xen&lt;/p&gt;
&lt;p&gt;Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.&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, Ubuntu:20.04:LTS: xen, Ubuntu:22.04:LTS: xen, Ubuntu:24.04:LTS: xen, Ubuntu:25.10: xen, Ubuntu:26.04:LTS: xen&lt;/p&gt;
&lt;p&gt;Xenstore: Guests can get access to Xenstore nodes of deleted domains Access rights of Xenstore nodes are per domid. When a domain is gone, there might be Xenstore nodes left with access rights containing the domid of the removed domain. This is normally no problem, as those access right entries will be corrected when such a node is written later. There is a small time window when a new domain is created, where the access rights of a past domain with the same domid as the new one will be regarded to be still valid, leading to the new domain being able to get access to a node which was meant to be accessible by the removed domain. For this to happen another domain needs to write the node before the newly created domain is being introduced to Xenstore by dom0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-42320</guid>
    </item>
    <item>
      <title>WID-SEC-W-2022-1939 — Xen: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1939</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xen und Citrix Systems Hypervisor ausnutzen um einen Denial of Service zu verursachen, Informationen offenzulegen oder seine Rechte zu erweitern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xen und Citrix Systems Hypervisor ausnutzen um einen Denial of Service zu verursachen, Informationen offenzulegen oder seine Rechte zu erweitern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1939</guid>
    </item>
  </channel>
</rss>
