3 ms·
What does 'not applicable' mean in this context? No problems or we don't have plans to fix it? Zen1/1+ doesn't seem present in these charts at all. Edit: It is
by yomlica8 3y ago
What does 'not applicable' mean in this context? No problems or we don't have plans to fix it? Zen1/1+ doesn't seem present in these charts at all.
Edit: It is actually mentioned if you do something clever like read.
> No µcode patch or BIOS update, which includes the µcode patch, is necessary for products based on “Zen” or “Zen 2” CPU architectures because these architectures are already designed to flush branch type predictions from the branch predictor.
- tetumetal 3y agoThe original video from the authors of inception runs on a zen4. But, the authors also claim that zen2 is vulnerable to the exploit. However, in zen2, KASLR cannot be broken by inception, in a reasonable time. So, the authors proposed to install a kernel module to get the kernel address. Then, pass this address to the exploit: https://github.com/comsec-group/inception/tree/master/inception/zen_1_2 https://github.com/comsec-group/inception/tree/master/incept... From the practical point of view, it does not make sense to require the installation of a kernel module to get some information needed by the exploit. It's kind of a cheat. If I can install a kernel module, it means that I already have root access. So, in my opinion, from the practical point of view KASLR is enough to mitigate inception in zen1,2. The authors claim that this architectures can be exploited it's an overstatement.