The XEN_DOMCTL_memory_mapping hypercall allows long running operations
without implementing preemption.
This hypercall is used by the device model as part of the emulation
associated with configuration of PCI devices passed through to HVM
guests and is therefore indirectly exposed to those guests.
This can cause a physical CPU to become busy for a significant period,
leading to a host denial of service in some cases.
If a host denial of service is not triggered then it may instead be
possible to deny service to the domain running the device model,
e.g. domain 0.
This hypercall is also exposed more generally to all
toolstacks. However the uses of it in libxl based toolstacks are not
believed to open up any avenue of attack from an untrusted
guest. Other toolstacks may be vulnerable however.
The vulnerability is exposed via HVM guests which have a PCI device
assigned to them. A malicious HVM guest in such a configuration can
mount a denial of service attack affecting the whole system via its
associated device model (qemu-dm).
A guest is able to trigger this hypercall via operations which it is
legitimately expected to perform, therefore running the device model
as a stub domain does not offer protection against the host denial of
service issue. However it does offer some protection against secondary
issues such as denial of service against dom0.
The issue is exposed via x86 HVM VMs which have been assigned a PCI
x86 PV domains, x86 HVM domains without passthrough devices and ARM
domains do not expose this vulnerability.
Xen 3.2.x and later are vulnerable.
Xen 3.1.x and earlier have not been inspected.
Running only PV guests will avoid this issue.
This issue can be avoided by not assigning devices with large MMIO
regions to untrusted HVM guests.
Applying the appropriate attached patch resolves this issue.
Created attachment 1003859 [details]
Created attachment 1003861 [details]
Created xen tracking bugs for this issue:
Affects: fedora-all [bug 1207741]
Red Hat would like to thank the Xen for reporting this issue.
This issue dos affect the kernel-xen packages as shipped with Red Hat Enterprise Linux 5.
Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
Created attachment 1009170 [details]
Created attachment 1009171 [details]
Created attachment 1009172 [details]
Created attachment 1009173 [details]
The supplied xsa125-4.x.patch did not apply cleanly to Xen 4.3.x or
4.2.x possibly resulting in a source tree which did not build.
Separate patches are now supplied for 4.3.x and 4.2.x.