The flaw in the mshv_handle_gpa_intercept routine causes every fault on movable memory regions to be remapped without verifying if the access that caused the fault is actually allowed. If a guest writes to a read‑only area or attempts an execute in a non‑executable region, the remap succeeds but the page remains protected, leading the guest to fault again immediately. This cycle repeats indefinitely, spinning the virtual CPU and consuming host CPU cycles, which can be triggered intentionally by a malicious virtual machine. This behavior constitutes an infinite loop (CWE‑835) and is a form of denial‑of‑service vulnerability.

All Linux kernel builds that include the Hyper‑V (mshv) virtual machine monitor component are potentially affected, regardless of the exact kernel release. The CVE data does not list specific kernel versions; the fix is contained in commits 02226839 and 16cbec24 in the kernel source tree, so any kernel that has not merged those commits may still be vulnerable.

The CVSS score of 5.5 indicates a medium severity. The exploitability is low in terms of public threat: the EPSS score is reported as < 1 % and the vulnerability is not listed in CISA’s KEV catalog, indicating no publicly known exploits. However, the vulnerability can still be triggered by a guest that has permission to load the Hyper‑V module and control memory permissions, which could lead to a denial of service of the host by exhausting CPU resources. The attack vector is therefore a malicious guest impersonating normal workload inside the same host or a compromised hypervisor setting up the faulty permissions.