CVE-2012-6031

2012-11-2300:00:00

ubuntu.com

4.7 Medium

CVSS2

Access Vector

LOCAL

Access Complexity

MEDIUM

Authentication

NONE

Confidentiality Impact

NONE

Integrity Impact

NONE

Availability Impact

COMPLETE

AV:L/AC:M/Au:N/C:N/I:N/A:C

0.001 Low

EPSS

Percentile

25.9%

JSON

The do_tmem_get 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 (CPU hang
and host crash) via unspecified vectors related to a spinlock being held in
the “bad_copy 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.

Notes

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”

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”