First published: Wed Apr 13 2016(Updated: )
Xen 4.6.x, 4.5.x, 4.4.x, 4.3.x, and earlier do not initialize x86 FPU stack and XMM registers when XSAVE/XRSTOR are not used to manage guest extended register state, which allows local guest domains to obtain sensitive information from other domains via unspecified vectors.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
XenServer | =6.0 | |
Xen XAPI | =4.3.0 | |
Xen XAPI | =4.3.1 | |
Xen XAPI | =4.3.2 | |
Xen XAPI | =4.3.3 | |
Xen XAPI | =4.3.4 | |
Xen XAPI | =4.4.0 | |
Xen XAPI | =4.4.1 | |
Xen XAPI | =4.4.2 | |
Xen XAPI | =4.4.3 | |
Xen XAPI | =4.4.4 | |
Xen XAPI | =4.5.0 | |
Xen XAPI | =4.5.1 | |
Xen XAPI | =4.5.2 | |
Xen XAPI | =4.5.3 | |
Xen XAPI | =4.6.0 | |
Xen XAPI | =4.6.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-8555 has a medium severity rating that indicates potential risks of information disclosure.
To fix CVE-2015-8555, the affected version of Xen should be updated to a patched release that properly initializes the FPU stack and XMM registers.
CVE-2015-8555 affects installations of Xen 4.3.x through 4.6.x, including various XenServer versions.
CVE-2015-8555 exploits improper initialization of the FPU stack and XMM registers, allowing local guest domains to access sensitive information from other guest domains.
While CVE-2015-8555 has been addressed in later versions, systems running outdated versions of Xen remain at risk.