KVM: SEV: Do cache maintenance on the source VM during intra-host migration
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.55, 7.2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b56639318bb2be66aceba92836279714488709b4 · fixed in 37dfb676fafd1eef36fe0bb649607afbb0d5521b; From b56639318bb2be66aceba92836279714488709b4 · fixed in d4cc2dff12116a700add601c0262132cc26e1b2c; From b56639318bb2be66aceba92836279714488709b4 · fixed in 93de2a6a4b91b72607136dd656edf03fb399d27f
- Linux Linux
5.16
- KernelLinux
From 5.16.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9