<?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 23:26:21 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0941 — De multiples vulnérabilités ont été découvertes dans Citrix XenServer. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0941</link>
      <description>certfr-2026-avi-0941</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0941</guid>
    </item>
    <item>
      <title>EUVD-2026-342086</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342086</link>
      <description>EUVD-2026-342086</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342086</guid>
    </item>
    <item>
      <title>fkie_cve-2026-62435</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-62435</link>
      <description>&lt;p&gt;[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]&lt;/p&gt;
&lt;p&gt;With the introduction of Grant Table v2 came the requirement to be able to
switch between versions.  Switching from v1 to v2 reduces the number of
valid grant references, as a bigger shared entry structure is then needed
while the shared table doesn&amp;#39;t change size.  Switching from v2 back to v1
the status frames, which are separate in v2, go away.&lt;/p&gt;
&lt;p&gt;Code holding, but intermediately dropping and then re-acquiring the grant
table lock, sometimes wrongly assumes that said properties wouldn&amp;#39;t change
across the window in time where the lock is not being held.&lt;/p&gt;
&lt;p&gt;The v1 -&amp;gt; v2 issue is CVE-2026-62435.&lt;/p&gt;
&lt;p&gt;The v2 -&amp;gt; v1 issue is CVE-2026-62436.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]&lt;/p&gt;
&lt;p&gt;With the introduction of Grant Table v2 came the requirement to be able to
switch between versions.  Switching from v1 to v2 reduces the number of
valid grant references, as a bigger shared entry structure is then needed
while the shared table doesn&amp;#39;t change size.  Switching from v2 back to v1
the status frames, which are separate in v2, go away.&lt;/p&gt;
&lt;p&gt;Code holding, but intermediately dropping and then re-acquiring the grant
table lock, sometimes wrongly assumes that said properties wouldn&amp;#39;t change
across the window in time where the lock is not being held.&lt;/p&gt;
&lt;p&gt;The v1 -&amp;gt; v2 issue is CVE-2026-62435.&lt;/p&gt;
&lt;p&gt;The v2 -&amp;gt; v1 issue is CVE-2026-62436.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-62435</guid>
    </item>
    <item>
      <title>GHSA-38wq-hqmp-4jj6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-38wq-hqmp-4jj6</link>
      <description>&lt;p&gt;[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]&lt;/p&gt;
&lt;p&gt;With the introduction of Grant Table v2 came the requirement to be able to
switch between versions.  Switching from v1 to v2 reduces the number of
valid grant references, as a bigger shared entry structure is then needed
while the shared table doesn&amp;#39;t change size.  Switching from v2 back to v1
the status frames, which are separate in v2, go away.&lt;/p&gt;
&lt;p&gt;Code holding, but intermediately dropping and then re-acquiring the grant
table lock, sometimes wrongly assumes that said properties wouldn&amp;#39;t change
across the window in time where the lock is not being held.&lt;/p&gt;
&lt;p&gt;The v1 -&amp;gt; v2 issue is CVE-2026-62435.&lt;/p&gt;
&lt;p&gt;The v2 -&amp;gt; v1 issue is CVE-2026-62436.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]&lt;/p&gt;
&lt;p&gt;With the introduction of Grant Table v2 came the requirement to be able to
switch between versions.  Switching from v1 to v2 reduces the number of
valid grant references, as a bigger shared entry structure is then needed
while the shared table doesn&amp;#39;t change size.  Switching from v2 back to v1
the status frames, which are separate in v2, go away.&lt;/p&gt;
&lt;p&gt;Code holding, but intermediately dropping and then re-acquiring the grant
table lock, sometimes wrongly assumes that said properties wouldn&amp;#39;t change
across the window in time where the lock is not being held.&lt;/p&gt;
&lt;p&gt;The v1 -&amp;gt; v2 issue is CVE-2026-62435.&lt;/p&gt;
&lt;p&gt;The v2 -&amp;gt; v1 issue is CVE-2026-62436.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-38wq-hqmp-4jj6</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-62435</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-62435</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;[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] With the introduction of Grant Table v2 came the requirement to be able to switch between versions.  Switching from v1 to v2 reduces the number of valid grant references, as a bigger shared entry structure is then needed while the shared table doesn&amp;#39;t change size.  Switching from v2 back to v1 the status frames, which are separate in v2, go away. Code holding, but intermediately dropping and then re-acquiring the grant table lock, sometimes wrongly assumes that said properties wouldn&amp;#39;t change across the window in time where the lock is not being held. The v1 -&amp;gt; v2 issue is CVE-2026-62435. The v2 -&amp;gt; v1 issue is CVE-2026-62436.&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;[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] With the introduction of Grant Table v2 came the requirement to be able to switch between versions.  Switching from v1 to v2 reduces the number of valid grant references, as a bigger shared entry structure is then needed while the shared table doesn&amp;#39;t change size.  Switching from v2 back to v1 the status frames, which are separate in v2, go away. Code holding, but intermediately dropping and then re-acquiring the grant table lock, sometimes wrongly assumes that said properties wouldn&amp;#39;t change across the window in time where the lock is not being held. The v1 -&amp;gt; v2 issue is CVE-2026-62435. The v2 -&amp;gt; v1 issue is CVE-2026-62436.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-62435</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2568 — Xen: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2568</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Xen ausnutzen, um seine Privilegien zu erhöhen, vertrauliche Informationen 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 seine Privilegien zu erhöhen, vertrauliche Informationen 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-2568</guid>
    </item>
  </channel>
</rss>
