Windows Hyper-V Security Feature Bypass Vulnerability

According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do?
Successful exploitation of this vulnerability by an attacker requires a user to first reboot their machine.

What kind of security feature could be bypassed by successfully exploiting this vulnerability?
This Hypervisor vulnerability relates to Virtual Machines within a Unified Extensible Firmware Interface (UEFI) host machine. On some specific hardware it might be possible to bypass the UEFI, which could lead to the compromise of the hypervisor and the secure kernel.

According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability?
Successful exploitation of this vulnerability requires multiple conditions to be met, such as specific application behavior, user actions, manipulation of parameters passed to a function, and impersonation of an integrity level token.

According to the CVSS metric, the attack vector is adjacent (AV:A). What does that mean for this vulnerability?
Successful exploitation of this vulnerability requires that an attacker will need to first gain access to the restricted network before running an attack.

Security updates
10.0.17763.6414 — https://support.microsoft.com/help/5044277
10.0.20348.2762 — https://support.microsoft.com/help/5044281
10.0.22000.3260 — https://support.microsoft.com/help/5044280
10.0.19044.5011 — https://support.microsoft.com/help/5044273
10.0.22621.4317 — https://support.microsoft.com/help/5044285
10.0.25398.1189 — https://support.microsoft.com/help/5044288
10.0.26100.2033 — https://support.microsoft.com/help/5044284