CVE-2012-6030

Publication date 23 November 2012

Last updated 24 July 2024


Ubuntu priority

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.

Read the notes from the security team

Status

Package Ubuntu Release Status
xen 12.10 quantal Ignored
12.04 LTS precise Ignored
11.10 oneiric Ignored
11.04 natty Not in release
10.04 LTS lucid Not in release
8.04 LTS hardy Not in release
xen-3.1 12.10 quantal Not in release
12.04 LTS precise Not in release
11.10 oneiric Not in release
11.04 natty Not in release
10.04 LTS lucid Not in release
8.04 LTS hardy
Not affected
xen-3.2 12.10 quantal Not in release
12.04 LTS precise Not in release
11.10 oneiric Not in release
11.04 natty Not in release
10.04 LTS lucid Not in release
8.04 LTS hardy
Not affected
xen-3.3 12.10 quantal Not in release
12.04 LTS precise Not in release
11.10 oneiric Not in release
11.04 natty Ignored end of life
10.04 LTS lucid
Not affected
8.04 LTS hardy Not in release

Notes


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"