<?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 10:30:48 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98718</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98718</link>
      <description>&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;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/fkie_cve-2026-98718</guid>
    </item>
    <item>
      <title>GHSA-8j5c-4j8r-8m5m</title>
      <link>https://db.gcve.eu/vuln/ghsa-8j5c-4j8r-8m5m</link>
      <description>&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;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/ghsa-8j5c-4j8r-8m5m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98718</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98718</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state 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:   CPU1 in sev_migrate_from():     src-&amp;gt;active = false;   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.   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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state 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:   CPU1 in sev_migrate_from():     src-&amp;gt;active = false;   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.   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/ubuntu-cve-2026-98718</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
