![]() If L1 disables VMLOAD/VMSAVE intercepts, and doesn't enable
Virtual VMLOAD/VMSAVE (currently not supported for the nested hypervisor),
then VMLOAD/VMSAVE must operate on the L1 physical memory, which is only
possible by making L0 intercept these instructions.
Failure to do so allowed the nested guest to run VMLOAD/VMSAVE unintercepted,
and thus read/write portions of the host physical memory.
Fixes:
|
||
---|---|---|
.. | ||
avic.c | ||
nested.c | ||
pmu.c | ||
sev.c | ||
svm.c | ||
svm.h | ||
svm_onhyperv.c | ||
svm_onhyperv.h | ||
svm_ops.h | ||
vmenter.S |