[lkml]   [2022]   [Jul]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Virt Call depth tracking mitigation
On Tue, Jul 19, 2022 at 02:45:40PM +0000, Michael Kelley (LINUX) wrote:

> In Hyper-V, the hypercall page is *not* writable by the guest. Quoting
> from Section 3.13 in the Hyper-V TLFS:
> The hypercall page appears as an "overlay" to the GPA space; that is,
> it covers whatever else is mapped to the GPA range. Its contents are
> readable and executable by the guest. Attempts to write to the
> hypercall page will result in a protection (#GP) exception.
> And:
> After the interface has been established, the guest can initiate a
> hypercall. To do so, it populates the registers per the hypercall protocol
> and issues a CALL to the beginning of the hypercall page. The guest
> should assume the hypercall page performs the equivalent of a near
> return (0xC3) to return to the caller. As such, the hypercall must be
> invoked with a valid stack.

I'm hoping that these days you're following that 0xc3 with a 0xcc at the
very least ?

IIRC the whole hyper-v thing is negotiated using (virtual) MSRs, would
it be possible to write the address of a return thunk into an MSR and
have the hypervisor rewrite the hypercall page accordingly?

This is needed for the AMD jmp2ret thing anyway. Or you get to eat an
IBPB before every hypercall, which I'm guessing your performance people
aren't keen on.

 \ /
  Last update: 2022-07-19 22:17    [W:0.086 / U:0.912 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site