In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Do cache maintenance…

Why it is Yellow

• CVSS 7.1 high
• On your watchlist: linux kernel

References

• https://git.kernel.org/stable/c/37dfb676fafd1eef36fe0bb649607afbb0d5521b
• https://git.kernel.org/stable/c/93de2a6a4b91b72607136dd656edf03fb399d27f
• https://git.kernel.org/stable/c/d4cc2dff12116a700add601c0262132cc26e1b2c

Original description

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.