First published: Tue Aug 02 2016(Updated: )
Xen 4.5.x through 4.7.x do not implement Supervisor Mode Access Prevention (SMAP) whitelisting in 32-bit exception and event delivery, which allows local 32-bit PV guest OS kernels to cause a denial of service (hypervisor and VM crash) by triggering a safety check.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
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 | |
Xen XAPI | =4.6.3 | |
Xen XAPI | =4.7.0 | |
XenServer | =6.0 | |
XenServer | =6.0.2 | |
XenServer | =6.1 | |
XenServer | =6.2.0-sp1 | |
XenServer | =6.5.0-sp1 | |
XenServer | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-6259 has been classified as a moderate severity vulnerability due to its potential to cause denial of service.
To fix CVE-2016-6259, you need to upgrade to a patched version of Xen or XenServer that addresses the SMAP whitelisting issue.
CVE-2016-6259 affects Xen versions 4.5.x through 4.7.x.
No, CVE-2016-6259 requires local access to the 32-bit PV guest OS to exploit the vulnerability.
CVE-2016-6259 may lead to a denial of service, causing hypervisor and VM crashes.