https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 07 Nov 2026 05:00:18 +0000 https://db.gcve.eu/vuln/cve-2026-98471 <p><strong>Affected:</strong> Linux</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> <p><strong>Affected:</strong> Linux</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/cve-2026-98471