CVE-2026-0665: 
Wolfi vulnerability analysis and mitigation

CVE-2026-0665 is a heap off-by-one vulnerability in QEMU's KVM Xen guest support, specifically in the PHYSDEVOP_map_pirq hypercall handler. A malicious guest can exploit this flaw to trigger out-of-bounds heap accesses in the QEMU process via the emulated Xen physdev hypercall interface, potentially leading to denial of service or memory corruption. The vulnerability was reported by DARKNAVY (@DarkNavyOrg) and published on February 18, 2026. It carries a CVSS v3.1 base score of 6.5 (Medium/High) with a Changed scope, affecting the host QEMU process from a guest context (Feedly, Red Hat Bugzilla).

The root cause is an off-by-one error (CWE-787: Out-of-bounds Write) in QEMU's handling of the Xen PHYSDEVOP_map_pirq hypercall within the KVM Xen emulation layer. When a guest issues this hypercall, insufficient bounds checking allows a write or access one element beyond the intended heap buffer boundary, enabling out-of-bounds heap access. Exploitation requires low privileges (a guest OS user) and local access, but no user interaction, and the scope is changed — meaning the impact crosses from the guest into the host QEMU process. The upstream fix was committed to the QEMU project repository, and the original patch was submitted via the qemu-devel mailing list by the discoverer (Red Hat Bugzilla, QEMU Commit).

Successful exploitation allows a malicious guest to cause a denial of service (crash) of the QEMU host process, which would disrupt all virtual machines managed by that QEMU instance. In more severe scenarios, the out-of-bounds heap access could lead to memory corruption in the QEMU process, potentially enabling a guest-to-host escape or arbitrary code execution on the hypervisor host. Confidentiality impact is rated as none, but the availability impact is high and the changed scope indicates cross-boundary effects from guest to host (Feedly, Red Hat Bugzilla).

No public exploit code or in-the-wild exploitation has been reported for CVE-2026-0665 as of the available data. The EPSS score is very low at approximately 0.006%, indicating a low probability of near-term exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an attacker to have control of a guest VM running on a KVM host with Xen emulation enabled, limiting the attack surface to multi-tenant virtualization environments (Feedly).

1. Prerequisite: Attacker controls a guest VM running on a KVM hypervisor with Xen guest support enabled (i.e., QEMU configured with KVM Xen emulation).
2. Craft malicious hypercall: From within the guest, craft a PHYSDEVOP_map_pirq Xen hypercall with parameters designed to trigger the off-by-one boundary condition in QEMU's physdev hypercall handler.
3. Trigger out-of-bounds access: Issue the crafted hypercall from the guest, causing QEMU on the host to perform a heap read or write one element beyond the allocated buffer boundary.
4. Achieve DoS or memory corruption: Depending on heap layout, this may crash the QEMU process (denial of service) or corrupt adjacent heap memory, potentially enabling further exploitation such as code execution in the QEMU host process (Red Hat Bugzilla, Infinitsec Write-up).

• Process: Unexpected crash or termination of the QEMU process (qemu-system-x86_64 or similar) on the hypervisor host, potentially with a segmentation fault or heap corruption error in logs.
• Logs: System logs (/var/log/syslog, /var/log/messages, or journald) showing QEMU process crashes with signals such as SIGSEGV or SIGABRT, particularly following guest-initiated hypercall activity.
• Logs: QEMU error output referencing Xen physdev hypercall handling or unexpected memory access violations.
• Network: Unexpected guest VM downtime or host instability correlated with specific guest activity on KVM/Xen-emulated environments.

The upstream fix has been committed to the QEMU project repository (commit c7504ba2a560fd884557f6e5142f03b491aad0c7). Downstream distributions including Ubuntu (USN-8073-1), openSUSE, SUSE (SUSE-SU-202621883-1), and Debian have released patched packages — administrators should update QEMU packages to the latest available version from their distribution. As a workaround where patching is not immediately possible, disabling Xen guest support in KVM configurations (if not required) eliminates the attack surface (Ubuntu Advisory, SUSE Advisory, QEMU Commit).

The vulnerability was credited to DARKNAVY (@DarkNavyOrg), who submitted the patch via the qemu-devel mailing list. A technical write-up was published by Infinitsec detailing the heap off-by-one in kvm_xen_physdev_op_map_pirq. Multiple Linux distributions including Ubuntu, SUSE, openSUSE, and Debian responded promptly with security advisories and patched packages. Coverage was also noted in German Linux security outlet Pro-Linux.de (Red Hat Bugzilla, Infinitsec Write-up).