HIGH Introduced in 5.16
kvm SevMigration CacheFlush
CVE-2026-98471
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
KernelScan AI6.0MEDIUM
01Description
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.
02KernelScan AI Analysis
Risk summary
A host administrator with root privileges can trigger an SEV intra-host migration that leaves stale plaintext data in CPU caches after the source VM is destroyed. This could expose sensitive guest memory contents to subsequent workloads or the host, and may also cause memory corruption or VM instability. The issue affects systems running KVM with AMD SEV enabled in multi-tenant or cloud environments.
Vulnerability analysis
During SEV intra-host migration, the source VM is converted to a non-SEV VM before its memory regions are transferred to the destination. Because the SEV-active flag is cleared early, the kernel's normal memory reclaim paths — which would flush CPU caches for an SEV VM — no longer run for the source VM. The destination VM cannot reliably perform the flush because it may not have access to all the same memory regions. The fix adds an explicit cache writeback on the source VM immediately after clearing the SEV-active flag, ensuring no plaintext data remains in CPU caches before the VM is torn down. Exploitation requires local root or CAP_SYS_ADMIN access to initiate a migration on a host with AMD SEV hardware.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.18 | 5.16 | 6.18.55 | 37dfb676fafd |
| 7.2 | 5.16 | 7.2.9 | d4cc2dff1211 |
| mainline | 5.16 | 7.3 | 93de2a6a4b91 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Affected — no CIP fix yet (latest 6.12.114-cip34) |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.190-cip62) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |