<?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>Mon, 16 Nov 2026 19:05:06 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1302 — 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-1302</link>
      <description>certfr-2026-avi-1302</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1302</guid>
    </item>
    <item>
      <title>EUVD-2026-389784</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-389784</link>
      <description>EUVD-2026-389784</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-389784</guid>
    </item>
    <item>
      <title>fkie_cve-2026-79610</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-79610</link>
      <description>&lt;p&gt;XSA-501 was about issues with v1 -&amp;gt; v2 and v2 -&amp;gt; v1 changes racing certain
other grant table operations.  Sadly a v2 -&amp;gt; v1 -&amp;gt; v2 change has yet
another effect which wasn&amp;#39;t accounted for: During the first change, status
pages would be freed.  During the second change they would be allocated
again.  Hence across the full pair of change the addresses of the status
pages may change, rendering stale previously calculated pointers into the
status array.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;XSA-501 was about issues with v1 -&amp;gt; v2 and v2 -&amp;gt; v1 changes racing certain
other grant table operations.  Sadly a v2 -&amp;gt; v1 -&amp;gt; v2 change has yet
another effect which wasn&amp;#39;t accounted for: During the first change, status
pages would be freed.  During the second change they would be allocated
again.  Hence across the full pair of change the addresses of the status
pages may change, rendering stale previously calculated pointers into the
status array.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-79610</guid>
    </item>
    <item>
      <title>GHSA-mm4r-fcq9-pfr4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mm4r-fcq9-pfr4</link>
      <description>&lt;p&gt;XSA-501 was about issues with v1 -&amp;gt; v2 and v2 -&amp;gt; v1 changes racing certain
other grant table operations.  Sadly a v2 -&amp;gt; v1 -&amp;gt; v2 change has yet
another effect which wasn&amp;#39;t accounted for: During the first change, status
pages would be freed.  During the second change they would be allocated
again.  Hence across the full pair of change the addresses of the status
pages may change, rendering stale previously calculated pointers into the
status array.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;XSA-501 was about issues with v1 -&amp;gt; v2 and v2 -&amp;gt; v1 changes racing certain
other grant table operations.  Sadly a v2 -&amp;gt; v1 -&amp;gt; v2 change has yet
another effect which wasn&amp;#39;t accounted for: During the first change, status
pages would be freed.  During the second change they would be allocated
again.  Hence across the full pair of change the addresses of the status
pages may change, rendering stale previously calculated pointers into the
status array.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mm4r-fcq9-pfr4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-79610</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-79610</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.10: xen, Ubuntu:26.04:LTS: xen&lt;/p&gt;
&lt;p&gt;XSA-501 was about issues with v1 -&amp;gt; v2 and v2 -&amp;gt; v1 changes racing certain other grant table operations.  Sadly a v2 -&amp;gt; v1 -&amp;gt; v2 change has yet another effect which wasn&amp;#39;t accounted for: During the first change, status pages would be freed.  During the second change they would be allocated again.  Hence across the full pair of change the addresses of the status pages may change, rendering stale previously calculated pointers into the status array.&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.10: xen, Ubuntu:26.04:LTS: xen&lt;/p&gt;
&lt;p&gt;XSA-501 was about issues with v1 -&amp;gt; v2 and v2 -&amp;gt; v1 changes racing certain other grant table operations.  Sadly a v2 -&amp;gt; v1 -&amp;gt; v2 change has yet another effect which wasn&amp;#39;t accounted for: During the first change, status pages would be freed.  During the second change they would be allocated again.  Hence across the full pair of change the addresses of the status pages may change, rendering stale previously calculated pointers into the status array.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-79610</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3930 — Xen: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3930</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um beliebigen Code – möglicherweise sogar mit Root-Rechten – auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um beliebigen Code – möglicherweise sogar mit Root-Rechten – auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3930</guid>
    </item>
  </channel>
</rss>
