{"id":"CVE-2026-98471","title":"KVM: SEV: Do cache maintenance on the source VM during intra-host migration","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Do cache maintenance on the source VM during intra-host migration\n\nManually perform cache maintenance on the source VM during intra-host\nmigration to ensure n…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= b56639318bb2be66aceba92836279714488709b4 < 37dfb676fafd1eef36fe0bb649607afbb0d5521b","Linux >= b56639318bb2be66aceba92836279714488709b4 < d4cc2dff12116a700add601c0262132cc26e1b2c","Linux >= b56639318bb2be66aceba92836279714488709b4 < 93de2a6a4b91b72607136dd656edf03fb399d27f","Linux 5.16"],"published":"2026-10-18","updated":"2026-10-18","sourceUpdated":"2026-10-18T15:15:23.690Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98471","references":[{"url":"https://git.kernel.org/stable/c/37dfb676fafd1eef36fe0bb649607afbb0d5521b"},{"url":"https://git.kernel.org/stable/c/d4cc2dff12116a700add601c0262132cc26e1b2c"},{"url":"https://git.kernel.org/stable/c/93de2a6a4b91b72607136dd656edf03fb399d27f"}],"tags":["cve.org"],"ingestedAt":"2026-10-18T15:45:12.299Z","slug":"CVE-2026-98471","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Do cache maintenance on the source VM during intra-host migration\n\nManually perform cache maintenance on the source VM during intra-host\nmigration to ensure no stale data is left in CPU caches after the VM is\ndestroyed.  Because the source VM is \"converted\" to a non-SEV VM, KVM's\nmemory reclaim flows won't trigger cache maintenance, e.g. when all guest\nmemory is reclaimed in response to detaching from the mmu_notifier.\n\nNote, relying on the destination VM to do cache maintenance isn't an option\nas KVM doesn't require identical guest memory configurations, i.e. the\nsource VM may have access to memory that the destination VM does not.\nEnforcing equivalent memory configurations is infeasible, as it would\nrequire a *deep* comparison of memslots, e.g. to verify that not only are\nthe memslot identical, but what the memslots point at is also identical.\n\n## Affected\n\n- `Linux >= b56639318bb2be66aceba92836279714488709b4 < 37dfb676fafd1eef36fe0bb649607afbb0d5521b`\n- `Linux >= b56639318bb2be66aceba92836279714488709b4 < d4cc2dff12116a700add601c0262132cc26e1b2c`\n- `Linux >= b56639318bb2be66aceba92836279714488709b4 < 93de2a6a4b91b72607136dd656edf03fb399d27f`\n- `Linux 5.16`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}