https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 07 Nov 2026 04:34:00 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1469 certfr-2026-avi-1469 https://db.gcve.eu/vuln/certfr-2026-avi-1469 https://db.gcve.eu/vuln/fkie_cve-2026-98471 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Do cache maintenance on the source VM during intra-host migration</p> <p>Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is &#34;converted&#34; to a non-SEV VM, KVM&#39;s memory reclaim flows won&#39;t trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier.</p> <p>Note, relying on the destination VM to do cache maintenance isn&#39;t an option as KVM doesn&#39;t require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Do cache maintenance on the source VM during intra-host migration</p> <p>Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is &#34;converted&#34; to a non-SEV VM, KVM&#39;s memory reclaim flows won&#39;t trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier.</p> <p>Note, relying on the destination VM to do cache maintenance isn&#39;t an option as KVM doesn&#39;t require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98471 https://db.gcve.eu/vuln/ghsa-hqmw-j6g2-75m9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Do cache maintenance on the source VM during intra-host migration</p> <p>Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is &#34;converted&#34; to a non-SEV VM, KVM&#39;s memory reclaim flows won&#39;t trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier.</p> <p>Note, relying on the destination VM to do cache maintenance isn&#39;t an option as KVM doesn&#39;t require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: SEV: Do cache maintenance on the source VM during intra-host migration</p> <p>Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is &#34;converted&#34; to a non-SEV VM, KVM&#39;s memory reclaim flows won&#39;t trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier.</p> <p>Note, relying on the destination VM to do cache maintenance isn&#39;t an option as KVM doesn&#39;t require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.</p> https://db.gcve.eu/vuln/ghsa-hqmw-j6g2-75m9 https://db.gcve.eu/vuln/msrc_cve-2026-98471 msrc_CVE-2026-98471 https://db.gcve.eu/vuln/msrc_cve-2026-98471 https://db.gcve.eu/vuln/suse-su-2026:24550-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://db.gcve.eu/vuln/suse-su-2026:24550-1 https://db.gcve.eu/vuln/ubuntu-cve-2026-98471 <p><strong>Affected:</strong> 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 155 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance on the source VM during intra-host migration Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is &#34;converted&#34; to a non-SEV VM, KVM&#39;s memory reclaim flows won&#39;t trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier. Note, relying on the destination VM to do cache maintenance isn&#39;t an option as KVM doesn&#39;t require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.</p> <p><strong>Affected:</strong> 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 155 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance on the source VM during intra-host migration Manually perform cache maintenance on the source VM during intra-host migration to ensure no stale data is left in CPU caches after the VM is destroyed. Because the source VM is &#34;converted&#34; to a non-SEV VM, KVM&#39;s memory reclaim flows won&#39;t trigger cache maintenance, e.g. when all guest memory is reclaimed in response to detaching from the mmu_notifier. Note, relying on the destination VM to do cache maintenance isn&#39;t an option as KVM doesn&#39;t require identical guest memory configurations, i.e. the source VM may have access to memory that the destination VM does not. Enforcing equivalent memory configurations is infeasible, as it would require a *deep* comparison of memslots, e.g. to verify that not only are the memslot identical, but what the memslots point at is also identical.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98471