PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspe…
xen
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
| No fix yet |
| Xen xen |
|
|
| Xen xen |
| No fix yet |
xen
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
| No fix yet |
| Xen xen |
|
|
| Xen xen |
| No fix yet |
PoD operations on misaligned GFNs T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] x86 HVM and PVH guests may be started in populate-on-demand (PoD) mode, to provide a way for them to later easily have more memory assigned. Guests are permitted to control certain P2M aspects of individual pages via hypercalls. These hypercalls may act on ranges of pages specified via page orders (resulting in a power-of-2 number of pages). The implementation of some of these hypercalls for PoD does not enforce the base page frame number to be suitably aligned for the specified order, yet some code involved in PoD handling actually makes such an assumption. These operations are XENMEM_decrease_reservation (CVE-2021-28704) and XENMEM_populate_physmap (CVE-2021-28707), the latter usable only by domains controlling the guest, i.e. a de-privileged qemu or a stub domain. (Patch 1, combining the fix to both these two issues.) In addition handling of XENMEM_decrease_reservation can also trigger a host crash when the specified page order is neither 4k nor 2M nor 1G (CVE-2021-28708, patch 2).
From the CVE record · XEN
Xen's populate-on-demand (PoD) handling for x86 HVM and PVH guests is vulnerable when XENMEM_decrease_reservation is called with a page order other than 4K, 2M, or 1G. A guest using the hypercall can trigger a host crash; no additional authentication or user interaction is described.
Operators running Xen with x86 HVM or PVH guests in PoD mode should check their deployments; affected versions are not specified.