<?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>Tue, 03 Nov 2026 13:10:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98718 — KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98718</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: Do cache maintenance on the source VM *before* clearing SEV state&lt;/p&gt;
&lt;p&gt;Explicitly flush caches after intra-host migration before clearing &amp;#34;SEV
active&amp;#34; on the source VM, as doing cache maintenance afterwards creates a
tiny window where memory reclaim could return memory to the host without
performing a cache flush, e.g. as pointed out by Sashiko:&lt;/p&gt;
&lt;p&gt;CPU1 in sev_migrate_from():
    src-&amp;gt;active = false;&lt;/p&gt;
&lt;p&gt;CPU2 running concurrent unmap:
    Since active is false, the automatic cache flush in
    sev_guest_memory_reclaimed is skipped.
    The host frees and reallocates the page.&lt;/p&gt;
&lt;p&gt;CPU1 in sev_migrate_from():
    sev_writeback_caches(src_kvm);
    Executes a hardware cache flush (wbnoinvd), which writes the guest&amp;#39;s old
    dirty ciphertext over the new page owner&amp;#39;s data.&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: Do cache maintenance on the source VM *before* clearing SEV state&lt;/p&gt;
&lt;p&gt;Explicitly flush caches after intra-host migration before clearing &amp;#34;SEV
active&amp;#34; on the source VM, as doing cache maintenance afterwards creates a
tiny window where memory reclaim could return memory to the host without
performing a cache flush, e.g. as pointed out by Sashiko:&lt;/p&gt;
&lt;p&gt;CPU1 in sev_migrate_from():
    src-&amp;gt;active = false;&lt;/p&gt;
&lt;p&gt;CPU2 running concurrent unmap:
    Since active is false, the automatic cache flush in
    sev_guest_memory_reclaimed is skipped.
    The host frees and reallocates the page.&lt;/p&gt;
&lt;p&gt;CPU1 in sev_migrate_from():
    sev_writeback_caches(src_kvm);
    Executes a hardware cache flush (wbnoinvd), which writes the guest&amp;#39;s old
    dirty ciphertext over the new page owner&amp;#39;s data.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98718</guid>
    </item>
  </channel>
</rss>
