Hacker News Reader

Is the mitigation something that has to be installed on every system boot and only protects against microcode exploits later on that boot?

View on HN

> The fix released by AMD modifies the microcode validation routine to use a custom secure hash function. This is paired with an AMD Secure Processor update which ensures the patch validation routine is updated before the x86 cores can attempt to install a tampered microcode patch.

What if your cpu microcode already has malware which injects itself into the microcode update?

https://dl.acm.org/doi/10.1145/358198.358210

CPUs don't have non-volatile storage for microcode updates; it gets uploaded on boot from a copy stored alongside the other firmware in a flash chip on the motherboard, or optionally later in the boot process when an OS loads a microcode update from some other storage device. So a malicious microcode update that's trying to persist itself doesn't have to monitor for attempts to update CPU microcode, it has to detect attempts to install a BIOS update that includes a microcode update, find and poison the microcode update embedded within that BIOS update, and subvert any attempt to checksum the flash contents before rebooting. Fitting an attack that complex into CPU microcode patches that are on the order of a kilobyte is extremely implausible.

I would guess it is a BIOS patch, just like the microcode normally is.

So it probably needs to be installed at every system boot.

Perhaps someone more knowledgeable can correct my guesses?

Reply on news.ycombinator.com