guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be…
xen
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
| No fix yet |
| Xen xen |
|
|
| Xen xen |
| No fix yet |
| Xen xen |
|
xen
| Product | Affected | Fixed in |
|---|---|---|
| Xen xen |
| No fix yet |
| Xen xen |
|
|
| Xen xen |
| No fix yet |
| Xen xen |
|
| No fix yet |
guests may exceed their designated memory limit When a guest is permitted to have close to 16TiB of memory, it may be able to issue hypercalls to increase its memory allocation beyond the administrator established limit. This is a result of a calculation done with 32-bit precision, which may overflow. It would then only be the overflowed (and hence small) number which gets compared against the established upper bound.
From the CVE record · XEN
A 32-bit calculation in Xen may overflow when a guest is permitted close to 16 TiB of memory. A guest in that configuration may issue hypercalls to increase its memory allocation beyond the administrator-established limit. This requires access to the guest; no user interaction is described.
Administrators running Xen with guests permitted close to 16 TiB of memory should check their deployments; affected versions are not specified.