KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 12c1f6e03f944e399bd2c88441dca5dc702b95a5, Kernel 6aef7cf800098749ff5d660222efaf6e01e98c09 and Kernel 9784e5ca91b37b387f3f414af4340c54f7a63566.
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV Unconditionally free SEV's "have run CPUs" cpumask in the VM destroy path, i.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV VM if its state is intra-host migrated. Alternatively, the mask could be freed in sev_migrate_from() when "converting" the source VM, but that gets annoying because ideally KVM would nullify the mask to guard against UAF, and nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y. Freeing the mask during sev_migrate_from() is also not robust against other KVM bugs, though that's kind of a moot point since any such bugs would show up even if sev->active is never set. I.e. KVM must get that side of things correct. But, that's not a great reason to add more code just to make things marginally less robust.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=6f38f8c574642a822f2e85f079fa29a49176c49c <12c1f6e03f944e399bd2c88441dca5dc702b95a5, >=6f38f8c574642a822f2e85f079fa29a49176c49c <6aef7cf800098749ff5d660222efaf6e01e98c09, >=6f38f8c574642a822f2e85f079fa29a49176c49c <9784e5ca91b37b387f3f414af4340c54f7a63566 | 12c1f6e03f944e399bd2c88441dca5dc702b95a5, 6aef7cf800098749ff5d660222efaf6e01e98c09, 9784e5ca91b37b387f3f414af4340c54f7a63566 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket