cross-posted from: https://lemmy.world/post/3115044
Oh no.
I'm glad I'm running AMD CPUs on the computers I actually use for anything that could be considered sensitive.
Are you sure AMD CPUs are safer?
https://arxiv.org/pdf/2108.04575.pdf
If the vulnerability is part of a feature designed for niche use cases, then it's far safer than one that affects general use. I highly doubt most people are going to run virtual machines, plus the main target is server hosts that use VMs to run multiple servers of the same type on the same box. I might run a VM at some point in the future, but when I do I'll take steps to avoid any issues, like only enabling virtualization in the first place when I need it. Sure, that means I need to boot into the UEFI before and after every time I run a VM, but that's not an issue on the system I'd be running it on. And I'd rather have that inconvenience than have to worry about a vulnerability at all times.
In short, it's a matter of risk management.
im honestly not really surprised anymore. i fully expect to see a lot more of these types of bugs in the coming years