An issue was discovered in Xen through 4.12.x allowing ARM guest OS users to cause a denial of service via a XENMEMaddtophysmap hypercall. p2m->maxmappedgfn is used by the functions p2mresolvetranslationfault() and p2mgetentry() to sanity check guest physical frame. The rest of the code in the two functions will assume that there is a valid root table and check that with BUGON(). The function p2mgetrootpointer() will ignore the unused top bits of a guest physical frame. This means that the function p2msetentry() will alias the frame. However, p2m->maxmappedgfn will be updated using the original frame. It would be possible to set p2m->maxmappedgfn high enough to cover a frame that would lead p2mgetrootpointer() to return NULL in p2mgetentry() and p2mresolvetranslationfault(). Additionally, the sanity check on p2m->maxmappedgfn is off-by-one allowing "highest mapped + 1" to be considered valid. However, p2mgetrootpointer() will return NULL. The problem could be triggered with a specially crafted hypercall XENMEMaddtophysmap{, batch} followed by an access to an address (via hypercall or direct access) that passes the sanity check but cause p2mgetrootpointer() to return NULL. A malicious guest administrator may cause a hypervisor crash, resulting in a Denial of Service (DoS). Xen version 4.8 and newer are vulnerable. Only Arm systems are vulnerable. x86 systems are not affected.
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "xen-doc": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxengnttab1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxendevicemodel1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-4.11-armhf": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-4.9-armhf": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenevtchn1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxentoolcore1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxentoollog1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-common": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-4.9-arm64": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenforeignmemory1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxencall1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-utils-common-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-utils-4.11-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenmisc4.11-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-system-arm64": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xenstore-utils-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenstore3.0": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-4.11-arm64": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxengnttab1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenstore3.0-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-4.9-amd64": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenforeignmemory1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxendevicemodel1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxen-dev": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-system-amd64": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxentoolcore1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxencall1-dbgsym": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xenstore-utils": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenevtchn1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-utils-common": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-system-armhf": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxentoollog1": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-hypervisor-4.11-amd64": "4.11.3+24-g14b62ab3e5-1ubuntu1", "xen-utils-4.11": "4.11.3+24-g14b62ab3e5-1ubuntu1", "libxenmisc4.11": "4.11.3+24-g14b62ab3e5-1ubuntu1" } ] }