<?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>Wed, 07 Oct 2026 03:04:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-62436 — grant-table: version change racing with other operations</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-62436</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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.]&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;&lt;strong&gt;Affected:&lt;/strong&gt; 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.]&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/cve-2026-62436</guid>
    </item>
  </channel>
</rss>
