<?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://db.gcve.eu</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>Thu, 12 Nov 2026 07:21:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98472 — KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98472</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV&lt;/p&gt;
&lt;p&gt;Unconditionally free SEV&amp;#39;s &amp;#34;have run CPUs&amp;#34; cpumask in the VM destroy path,
i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV
VM if its state is intra-host migrated.  Alternatively, the mask could be
freed in sev_migrate_from() when &amp;#34;converting&amp;#34; the source VM, but that gets
annoying because ideally KVM would nullify the mask to guard against UAF,
and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.&lt;/p&gt;
&lt;p&gt;Freeing the mask during sev_migrate_from() is also not robust against other
KVM bugs, though that&amp;#39;s kind of a moot point since any such bugs would show
up even if sev-&amp;gt;active is never set.  I.e. KVM must get that side of things
correct.  But, that&amp;#39;s not a great reason to add more code just to make
things marginally less robust.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV&lt;/p&gt;
&lt;p&gt;Unconditionally free SEV&amp;#39;s &amp;#34;have run CPUs&amp;#34; cpumask in the VM destroy path,
i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV
VM if its state is intra-host migrated.  Alternatively, the mask could be
freed in sev_migrate_from() when &amp;#34;converting&amp;#34; the source VM, but that gets
annoying because ideally KVM would nullify the mask to guard against UAF,
and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.&lt;/p&gt;
&lt;p&gt;Freeing the mask during sev_migrate_from() is also not robust against other
KVM bugs, though that&amp;#39;s kind of a moot point since any such bugs would show
up even if sev-&amp;gt;active is never set.  I.e. KVM must get that side of things
correct.  But, that&amp;#39;s not a great reason to add more code just to make
things marginally less robust.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98472</guid>
    </item>
  </channel>
</rss>
