On Sun, 2026-09-20 at 21:57 +0000, [email protected] wrote: > [Severity: High] > Does this allow an untrusted L1 guest to crash the VM by triggering a > KVM_EXIT_INTERNAL_ERROR? The L1 guest can write a non-page-aligned > address to the APIC_ACCESS_ADDR field in vmcs12 and execute VMLAUNCH.
No, that would be caught by nested_vmx_check_apic_access_controls() which calls page_address_valid() and requires page alignment. So the VMLAUNCH should fail. (... s/should/does/ fail, as I made my friend throw up a self-test to prove it. Want that added to the existing tests?) > [Severity: Medium] > Will this nested lock cause an AB-BA circular locking dependency > warning from lockdep? No, RCU isn't really a 'lock'; those nest just fine (unlike the special case I just fixed in EVTCHNOP_send which was spinning inside the read section, waiting for something that could never complete until it *left* the read section — a completely different kind of deadlock).
smime.p7s
Description: S/MIME cryptographic signature
