On 09/05/2016 23:08, Tom Lendacky wrote: > On 05/09/2016 10:13 AM, Paolo Bonzini wrote: >> >> >> On 02/05/2016 20:31, Andy Lutomirski wrote: >>> And did the SEV implementation remember to encrypt the guest register >>> state? Because, if not, everything of importance will leak out >>> through the VMCB and/or GPRs. >> >> No, it doesn't. And SEV is very limited unless you paravirtualize >> everything. >> >> For example, the hypervisor needs to read some instruction bytes from >> memory, and instruction bytes are always encrypted (15.34.5 in the APM). >> So you're pretty much restricted to IN/OUT operations (not even >> INS/OUTS) on emulated (non-assigned) devices, paravirtualized MSRs, and >> hypercalls. These are the only operations that connect the guest and >> the hypervisor, where the vmexit doesn't have the need to e.g. walk >> guest page tables (also always encrypted). It possibly can be made to >> work once the guest boots, and a modern UEFI firmware probably can cope >> with it too just like a kernel can, but you need to ensure that your >> hardware has no memory BARs for example. And I/O port space is not very >> abundant. > > The instruction bytes stored in the VMCB at offset 0xd0 for a data > side #NPF are stored un-encrypted (which is not clearly documented in > the APM). This allows for the hypervisor to perform MMIO on emulated > devices. Because the hardware provides enough information on VMEXIT > events, such as exit codes, decode assist, etc., the hypervisor has > the information it needs to perform the operation Ok, that helps. >> In general, SEV provides mitigation only. Even if the hypervisor cannot >> write known plaintext directly to memory, an accomplice virtual machine >> can e.g. use the network to spray the attacked VM's memory. At least > > Can you elaborate further on this? The accomplice VM will not have > access to the encryption key of the target VM and cannot accomplish > any spraying that the hypervisor itself cannot do. It can send plaintext packets that will be stored encrypted in memory. (Of course the hypervisor can do that too if it has access to the guest network). This was my first thought on attacking SEV, but luckily NX is designed well. > In this first generation of SEV, we are targeting a threat model very > similar to the one used by SMEP and SMAP. And that's great! However, it is very different from "virtual machines need not fully trust the hypervisor and administrator of their host system" as said in the whitepaper. SEV protects pretty well from sibling VMs, but by design this generation of SEV leaks a lot of information to an evil host---probably more than enough to mount a ROP attack or to do evil stuff that Andy outlined. My problem is that people will read AMD's whitepaper, not your message on LKML, and may put more trust in SEV than (for now) they should. Thanks, Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
