4 ms·
OK, so this works on AMD Jaguar according to the README. That's a architecture from 2013. There's notes about Zen 3 having a different base address for the memo
by gmueckl 2mo ago
OK, so this works on AMD Jaguar according to the README. That's a architecture from 2013. There's notes about Zen 3 having a different base address for the memory controller registers, but that's it. What newer CPUs does attack actually work on?
- CartwheelLinux 2mo agoThat information is intentionally left out
- gmueckl 2mo agoThen publishing it in this incomplete state is just pointless fearmongering and will just make others fill in this information within the next couple of days. And the good guys likely won't be the first ones to do that.
- tecleandor 2mo agoIt's on the second paragraph, titled "Target". > Developed and tested on AMD Family 16h CPUs, the last generation whose datasheets document the DRAM controller's translation registers
- Cthulhu_ 2mo agoWhile security by obscurity isn't recommended, in this case it sounds like it's still a huge hurdle.
- fc417fc802 2mo agoYes, a hurdle to effective security research. Something hidden only appears to have no vulnerabilities. By raising the bar on a mass market product of this sort you ensure that in the event well funded actors develop exploits in secret they won't be inadvertently discovered by the public.
- devttyeu 2mo agoZen has completely different memory controller IP (UMC), that's configured at boot by AGESA/PSP. I doubt this exploit applies to modern Zen CPUs, however AMD are the only ones who could really confirm this.
- zerohp 2mo agoCPU designers have been aware of this attack vector for a while, so many (maybe all) have controls to lock these registers. They are written and locked by vendor firmware before it hands off to the operating system. You would have first break the firmware or locks before an attack like this on a modern CPU