<?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>Fri, 02 Oct 2026 13:41:31 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1136 — 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-2026-avi-1136</link>
      <description>certfr-2026-avi-1136</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1136</guid>
    </item>
    <item>
      <title>EUVD-2026-366570</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-366570</link>
      <description>EUVD-2026-366570</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-366570</guid>
    </item>
    <item>
      <title>fkie_cve-2026-62437</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-62437</link>
      <description>&lt;p&gt;When guests are terminated, various pieces of cleanup need carrying out.
The cleaning up of PCI devices which were assigned to guests, and the
associated removal of tracking structures for IRQs used by the devices
occurs relatively early in the process.  Unfortunately after that point
the guest about to be terminated could cause its device model (DM) to
re-establish such tracking structures, by having it bind one or more IRQs
anew.  While some of those tracking structures would still be cleaned up
later on, at least one would not be.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When guests are terminated, various pieces of cleanup need carrying out.
The cleaning up of PCI devices which were assigned to guests, and the
associated removal of tracking structures for IRQs used by the devices
occurs relatively early in the process.  Unfortunately after that point
the guest about to be terminated could cause its device model (DM) to
re-establish such tracking structures, by having it bind one or more IRQs
anew.  While some of those tracking structures would still be cleaned up
later on, at least one would not be.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-62437</guid>
    </item>
    <item>
      <title>GHSA-vfxv-3qcw-g966</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vfxv-3qcw-g966</link>
      <description>&lt;p&gt;When guests are terminated, various pieces of cleanup need carrying out.
The cleaning up of PCI devices which were assigned to guests, and the
associated removal of tracking structures for IRQs used by the devices
occurs relatively early in the process.  Unfortunately after that point
the guest about to be terminated could cause its device model (DM) to
re-establish such tracking structures, by having it bind one or more IRQs
anew.  While some of those tracking structures would still be cleaned up
later on, at least one would not be.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When guests are terminated, various pieces of cleanup need carrying out.
The cleaning up of PCI devices which were assigned to guests, and the
associated removal of tracking structures for IRQs used by the devices
occurs relatively early in the process.  Unfortunately after that point
the guest about to be terminated could cause its device model (DM) to
re-establish such tracking structures, by having it bind one or more IRQs
anew.  While some of those tracking structures would still be cleaned up
later on, at least one would not be.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vfxv-3qcw-g966</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11738-1 — xen-4.22.0_04-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11738-1</link>
      <description>&lt;p&gt;xen-4.22.0_04-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;xen-4.22.0_04-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11738-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:4087-1 — Security update for xen</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:4087-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-2026:4087-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-62437</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-62437</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:26.04:LTS: xen&lt;/p&gt;
&lt;p&gt;When guests are terminated, various pieces of cleanup need carrying out. The cleaning up of PCI devices which were assigned to guests, and the associated removal of tracking structures for IRQs used by the devices occurs relatively early in the process.  Unfortunately after that point the guest about to be terminated could cause its device model (DM) to re-establish such tracking structures, by having it bind one or more IRQs anew.  While some of those tracking structures would still be cleaned up later on, at least one would not be.&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:26.04:LTS: xen&lt;/p&gt;
&lt;p&gt;When guests are terminated, various pieces of cleanup need carrying out. The cleaning up of PCI devices which were assigned to guests, and the associated removal of tracking structures for IRQs used by the devices occurs relatively early in the process.  Unfortunately after that point the guest about to be terminated could cause its device model (DM) to re-establish such tracking structures, by having it bind one or more IRQs anew.  While some of those tracking structures would still be cleaned up later on, at least one would not be.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-62437</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3248 — Xen: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3248</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um einen Denial of Service Angriff durchzuführen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen und Daten zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um einen Denial of Service Angriff durchzuführen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen und Daten zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3248</guid>
    </item>
  </channel>
</rss>
