First published: Tue Jun 07 2016(Updated: )
The p2m_teardown function in arch/arm/p2m.c in Xen 4.4.x through 4.6.x allows local guest OS users with access to the driver domain to cause a denial of service (NULL pointer dereference and host OS crash) by creating concurrent domains and holding references to them, related to VMID exhaustion.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Xen xen-unstable | =4.4.0 | |
Xen xen-unstable | =4.4.0-rc1 | |
Xen xen-unstable | =4.4.1 | |
Xen xen-unstable | =4.4.2 | |
Xen xen-unstable | =4.4.3 | |
Xen xen-unstable | =4.4.4 | |
Xen xen-unstable | =4.5.0 | |
Xen xen-unstable | =4.5.1 | |
Xen xen-unstable | =4.5.2 | |
Xen xen-unstable | =4.5.3 | |
Xen xen-unstable | =4.6.0 | |
Xen xen-unstable | =4.6.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-5242 is considered a high severity vulnerability due to its potential to cause a denial of service by crashing the host OS.
To address CVE-2016-5242, users should upgrade to a patched version of Xen beyond 4.6.x that resolves the vulnerability.
CVE-2016-5242 enables local guest OS users to execute a denial of service attack against the host OS by exhausting VMIDs.
CVE-2016-5242 affects Xen versions 4.4.x through 4.6.x.
No, CVE-2016-5242 can only be exploited locally by guest OS users with access to the driver domain.