<?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>Sun, 04 Oct 2026 04:32:13 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0090 — De multiples vulnérabilités ont été découvertes dans Citrix XenServer. Elles permettent à un attaquant de provoquer un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0090</link>
      <description>certfr-2026-avi-0090</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0090</guid>
    </item>
    <item>
      <title>EUVD-2026-266837</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266837</link>
      <description>EUVD-2026-266837</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266837</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23553</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23553</link>
      <description>&lt;p&gt;In the context switch logic Xen attempts to skip an IBPB in the case of
a vCPU returning to a CPU on which it was the previous vCPU to run.
While safe for Xen&amp;#39;s isolation between vCPUs, this prevents the guest
kernel correctly isolating between tasks.  Consider:&lt;/p&gt;
&lt;p&gt;1) vCPU runs on CPU A, running task 1.
 2) vCPU moves to CPU B, idle gets scheduled on A.  Xen skips IBPB.
 3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB.
 4) vCPU moves back to CPU A.  Xen skips IBPB again.&lt;/p&gt;
&lt;p&gt;Now, task 2 is running on CPU A with task 1&amp;#39;s training still in the BTB.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the context switch logic Xen attempts to skip an IBPB in the case of
a vCPU returning to a CPU on which it was the previous vCPU to run.
While safe for Xen&amp;#39;s isolation between vCPUs, this prevents the guest
kernel correctly isolating between tasks.  Consider:&lt;/p&gt;
&lt;p&gt;1) vCPU runs on CPU A, running task 1.
 2) vCPU moves to CPU B, idle gets scheduled on A.  Xen skips IBPB.
 3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB.
 4) vCPU moves back to CPU A.  Xen skips IBPB again.&lt;/p&gt;
&lt;p&gt;Now, task 2 is running on CPU A with task 1&amp;#39;s training still in the BTB.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23553</guid>
    </item>
    <item>
      <title>GHSA-pxqc-5jg3-xfqm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pxqc-5jg3-xfqm</link>
      <description>&lt;p&gt;In the context switch logic Xen attempts to skip an IBPB in the case of
a vCPU returning to a CPU on which it was the previous vCPU to run.
While safe for Xen&amp;#39;s isolation between vCPUs, this prevents the guest
kernel correctly isolating between tasks.  Consider:&lt;/p&gt;
&lt;p&gt;1) vCPU runs on CPU A, running task 1.
 2) vCPU moves to CPU B, idle gets scheduled on A.  Xen skips IBPB.
 3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB.
 4) vCPU moves back to CPU A.  Xen skips IBPB again.&lt;/p&gt;
&lt;p&gt;Now, task 2 is running on CPU A with task 1&amp;#39;s training still in the BTB.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the context switch logic Xen attempts to skip an IBPB in the case of
a vCPU returning to a CPU on which it was the previous vCPU to run.
While safe for Xen&amp;#39;s isolation between vCPUs, this prevents the guest
kernel correctly isolating between tasks.  Consider:&lt;/p&gt;
&lt;p&gt;1) vCPU runs on CPU A, running task 1.
 2) vCPU moves to CPU B, idle gets scheduled on A.  Xen skips IBPB.
 3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB.
 4) vCPU moves back to CPU A.  Xen skips IBPB again.&lt;/p&gt;
&lt;p&gt;Now, task 2 is running on CPU A with task 1&amp;#39;s training still in the BTB.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pxqc-5jg3-xfqm</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10118-1 — xen-4.21.0_04-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10118-1</link>
      <description>&lt;p&gt;xen-4.21.0_04-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;xen-4.21.0_04-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10118-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0303-1 — Security update for xen</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0303-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:0303-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23553</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23553</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;In the context switch logic Xen attempts to skip an IBPB in the case of a vCPU returning to a CPU on which it was the previous vCPU to run. While safe for Xen&amp;#39;s isolation between vCPUs, this prevents the guest kernel correctly isolating between tasks.  Consider:  1) vCPU runs on CPU A, running task 1.  2) vCPU moves to CPU B, idle gets scheduled on A.  Xen skips IBPB.  3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB.  4) vCPU moves back to CPU A.  Xen skips IBPB again. Now, task 2 is running on CPU A with task 1&amp;#39;s training still in the BTB.&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;In the context switch logic Xen attempts to skip an IBPB in the case of a vCPU returning to a CPU on which it was the previous vCPU to run. While safe for Xen&amp;#39;s isolation between vCPUs, this prevents the guest kernel correctly isolating between tasks.  Consider:  1) vCPU runs on CPU A, running task 1.  2) vCPU moves to CPU B, idle gets scheduled on A.  Xen skips IBPB.  3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB.  4) vCPU moves back to CPU A.  Xen skips IBPB again. Now, task 2 is running on CPU A with task 1&amp;#39;s training still in the BTB.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23553</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0229 — Citrix Systems XenServer und Xen: Schwachstelle ermöglicht Offenlegung von Informationen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0229</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Citrix Systems XenServer und Xen ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Citrix Systems XenServer und Xen ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0229</guid>
    </item>
  </channel>
</rss>
