Live › vulnerability › CVE-2026-98471
Go to dashboardDuring intra-host migration of an SEV guest, the kernel's KVM code did not flush CPU caches for the source VM, so guest memory contents may remain in caches after the VM is destroyed. The sources do not state a concrete attacker outcome beyond leftover stale data.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only hosts running KVM with AMD SEV guests that use intra-host migration are relevant, since the flaw concerns cache maintenance when a source VM is converted to a non-SEV VM. Hosts without AMD SEV guests or without this migration path have little reason to act urgently. The sources do not say more about who is affected.
No product ranges from the sources yet.
uname -r to see the running kernel version and compare it against the fixed kernel release in the NVD entryEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 "converted" to a non-SEV VM, KVM's memory reclaim flows won'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't an option as KVM doesn'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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98471")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.