The Xen hypervisor contains a logic flaw in the handling of periodic Viridian STIMERs; the divisor used in a critical division operation is derived from user input and is not validated against zero. When an attacker supplies a zero divisor, the hypervisor triggers a #DE fault that crashes the impacted domain or the host system. This results in a denial of service for the affected guest or the entire hypervisor operation. The weakness is classed as CWE‑369, a classic divide‑by‑zero bug, and demonstrates how improper validation can cause a system crash.

The issue appears in Xen hypervisors that have Viridian extensions enabled for HVM guests. Because the extensions are not enabled by default, any Xen installation that has manually activated Viridian STIMERs for high‑virtual‑machine (HVM) guests and has not applied the security update referenced in XSA‑504 is vulnerable. No specific Xen version is enumerated, so the vulnerability may affect multiple releases that include the Viridian code path.

The CVSS score of 7.5 reflects a high severity denial of service impact. The EPSS score of < 1% signals a low likelihood of exploitation under current conditions, and the vulnerability is not listed in CISA's KEV catalog. Effective exploitation requires an attacker who can inject or influence the divisor value in a Viridian STIMER, which is inferred to mean control over a guest operating system or privileged user access to the hypervisor configuration. Thus, the attack vector is likely an insider or a compromised guest that can manipulate the STIMER settings, leading to a fault and system crash.