REDHAT-BUG-1477657: High severity Xen Project Xen vulnerability
ISSUE DESCRIPTION =================
When mapping a grant reference, a guest must inform Xen of where it would like the grant mapped. For PV guests, this is done by nominating an existing linear address, or an L1 pagetable entry, to be altered.
Neither of these PV paths check for alignment of the passed parameter. The linear address path suitably truncates the linear address when calculating the L1 entry to use, but the path which uses a directly nominated L1 entry performs no checks.
This causes Xen to make an incorrectly-aligned update to a pagetable, which corrupts both the intended entry and the subsequent entry with values which are largely guest controlled. If the misaligned value crosses a page boundary, then an arbitrary other heap page is corrupted.
IMPACT ======
A PV guest can elevate its privilege to that of the host.
VULNERABLE SYSTEMS ==================
All versions of Xen are vulnerable.
Only x86 systems are vulnerable.
Any system running untrusted PV guests is vulnerable.
The vulnerability is exposed to PV stub qemu serving as the device model for HVM guests. Our default assumption is that an HVM guest has compromised its PV stub qemu. By extension, it is likely that the vulnerability is exposed to HVM guests which are served by a PV stub qemu.
MITIGATION ==========
Running only HVM guests, served by a dom0-based qemu, will avoid this vulnerability.
External References:
http://xenbits.xen.org/xsa/advisory-227.html
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-1477657?
The severity of REDHAT-BUG-1477657 is classified as important because it may lead to memory corruption.
How do I fix REDHAT-BUG-1477657?
To fix REDHAT-BUG-1477657, you should apply the latest patches provided by the Xen Project.
What systems are affected by REDHAT-BUG-1477657?
REDHAT-BUG-1477657 affects Xen Project versions prior to the patched version.
What are the potential risks associated with REDHAT-BUG-1477657?
The potential risks of REDHAT-BUG-1477657 include increased vulnerability to memory manipulation and exploitation.
Is there a workaround for REDHAT-BUG-1477657?
Currently, there is no known workaround for REDHAT-BUG-1477657; upgrading is recommended.