7.2 High
CVSS2
Access Vector
LOCAL
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:L/AC:L/Au:N/C:C/I:C/A:C
0.001 Low
EPSS
Percentile
25.6%
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.
Author | Note |
---|---|
seth-arnold | Xen team strongly recommends against TMEM use |
mdeslaur | only 4.0 and higher ONLY installations where “tmem” is specified on the hypervisor command line are vulnerable. Most Xen installations do not do so. upstream says: “TMEM has been described by its maintainers as a technology preview, and is therefore not supported by them for use in production systems. Pending a full security audit of the code, the Xen.org security team recommends that Xen users do not enable TMEM.” We will not be fixing this in Ubuntu. Marking as “ignored” |
lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html
osvdb.org/85199
secunia.com/advisories/50472
wiki.xen.org/wiki/Security_Announcements#XSA-15_multiple_TMEM_hypercall_vulnerabilities
www.openwall.com/lists/oss-security/2012/09/05/8
www.securitytracker.com/id?1027482
xforce.iss.net/xforce/xfdb/78268
launchpad.net/bugs/cve/CVE-2012-6030
nvd.nist.gov/vuln/detail/CVE-2012-6030
security-tracker.debian.org/tracker/CVE-2012-6030
www.cve.org/CVERecord?id=CVE-2012-6030