----- dave.hansen@xxxxxxxxx wrote: > On 01/25/2018 06:11 PM, Liran Alon wrote: > > It is true that attacker cannot speculate to a kernel-address, but > it > > doesn't mean it cannot use the leaked kernel-address together with > > another unrelated vulnerability to build a reliable exploit. > > The address doesn't leak if you can't execute there. It's the same > reason that we don't worry about speculation to user addresses from > the > kernel when SMEP is in play. Maybe I misunderstand BTB & BHB internals. Will be glad if you could pinpoint my error. Google P0 blog-post (https://googleprojectzero.blogspot.co.il/2018/01/reading-privileged-memory-with-side.html) claims that BTB & BHB only use <31 low bits of the address of the source instruction to lookup into the BTB. In addition, it claims that the higher bits of the predicated destination change together with the higher bits of the source instruction. Therefore, it should be possible to leak the low bits of high predicition-mode code BTB/BHB entries from low prediction-mode code. Because the predicted destination address will reside in user-space. What am I missing? Thanks, -Liran
