First published: Fri Nov 23 2012(Updated: )
The do_tmem_op function in the Transcendent Memory (TMEM) in Xen 4.0, 4.1, and 4.2 allow local guest OS users to cause a denial of service (host crash) and possibly have other unspecified impacts via unspecified vectors related to "broken locking checks" in an "error path." NOTE: this issue was originally published as part of CVE-2012-3497, which was too general; CVE-2012-3497 has been SPLIT into this ID and others.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Xen xen-unstable | =4.0.0 | |
Xen xen-unstable | =4.1.0 | |
Xen xen-unstable | =4.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-6030 is classified as a high-severity vulnerability that can lead to denial of service and host crashes.
To address CVE-2012-6030, upgrade your Xen hypervisor to a version later than 4.2.0 that includes the necessary security patches.
CVE-2012-6030 affects Xen versions 4.0.0, 4.1.0, and 4.2.0.
CVE-2012-6030 is a local denial of service vulnerability that arises from broken locking checks in Transcendent Memory (TMEM) functionality.
There are no publicly known exploits for CVE-2012-6030, but the vulnerability allows local guests to potentially cause a host crash.