<?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 18:10:09 +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-389783</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-389783</link>
      <description>EUVD-2026-389783</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-389783</guid>
    </item>
    <item>
      <title>fkie_cve-2026-79611</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-79611</link>
      <description>&lt;p&gt;For XSA-308 logic was introduced, as VMX VMEntry checks do not like the
exact combination of state which occurs when #DB in intercepted, Single
Stepping is active, and blocked by STI/MovSS is active, despite this being
a legitimate state to be in.  The resulting VMEntry failure is fatal to
the guest.&lt;/p&gt;
&lt;p&gt;Sadly there is another special sub-case of the above, with branch tracing
enabled.  In that case the prior adjustment would still cause a VMentry
failure, as before fatal to the guest.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;For XSA-308 logic was introduced, as VMX VMEntry checks do not like the
exact combination of state which occurs when #DB in intercepted, Single
Stepping is active, and blocked by STI/MovSS is active, despite this being
a legitimate state to be in.  The resulting VMEntry failure is fatal to
the guest.&lt;/p&gt;
&lt;p&gt;Sadly there is another special sub-case of the above, with branch tracing
enabled.  In that case the prior adjustment would still cause a VMentry
failure, as before fatal to the guest.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-79611</guid>
    </item>
    <item>
      <title>GHSA-28w8-qvww-f539</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-28w8-qvww-f539</link>
      <description>&lt;p&gt;For XSA-308 logic was introduced, as VMX VMEntry checks do not like the
exact combination of state which occurs when #DB in intercepted, Single
Stepping is active, and blocked by STI/MovSS is active, despite this being
a legitimate state to be in.  The resulting VMEntry failure is fatal to
the guest.&lt;/p&gt;
&lt;p&gt;Sadly there is another special sub-case of the above, with branch tracing
enabled.  In that case the prior adjustment would still cause a VMentry
failure, as before fatal to the guest.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;For XSA-308 logic was introduced, as VMX VMEntry checks do not like the
exact combination of state which occurs when #DB in intercepted, Single
Stepping is active, and blocked by STI/MovSS is active, despite this being
a legitimate state to be in.  The resulting VMEntry failure is fatal to
the guest.&lt;/p&gt;
&lt;p&gt;Sadly there is another special sub-case of the above, with branch tracing
enabled.  In that case the prior adjustment would still cause a VMentry
failure, as before fatal to the guest.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-28w8-qvww-f539</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-79611</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-79611</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;For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in.  The resulting VMEntry failure is fatal to the guest. Sadly there is another special sub-case of the above, with branch tracing enabled.  In that case the prior adjustment would still cause a VMentry failure, as before fatal to the guest.&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;For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in.  The resulting VMEntry failure is fatal to the guest. Sadly there is another special sub-case of the above, with branch tracing enabled.  In that case the prior adjustment would still cause a VMentry failure, as before fatal to the guest.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-79611</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>
