CVE-2012-6035 json
The do_tmem_destroy_pool function in the Transcendent Memory (TMEM) in Xen 4.0, 4.1, and 4.2 does not properly validate pool ids, which all…
published 2012-11-23 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5909
- cvss
- 6.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
The do_tmem_destroy_pool function in the Transcendent Memory (TMEM) in Xen 4.0, 4.1, and 4.2 does not properly validate pool ids, which allows local guest OS users to cause a denial of service (memory corruption and host crash) or execute arbitrary code via unspecified vectors. 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.
Patch / fix
- xen Debian 14, Debian 13, Debian 12 4.1.4-1
debian advisories DEBIAN-CVE-2012-6035
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
security.gentoo.org
/glsa/glsa-201309-24.xml
vendor-advisory
-
security.gentoo.org
/glsa/201604-03
vendor-advisory
-
wiki.xen.org
/wiki/Security_Announcements#XSA-15_multiple_TMEM_hypercall_vulnerabilities
vendor-advisory
-
secunia.com
/advisories/50472
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/55082
third-party-advisory
-
securitytracker.com
/id?1027482
vdb-entry
-
securityfocus.com
/bid/55410
vdb-entry
-
openwall.com
/lists/oss-security/2012/09/05/8
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/78268
vdb-entry
-
osvdb.org
/85199
vdb-entry
-
lists.xen.org
/archives/html/xen-announce/2012-09/msg00006.html
mailing-list
Sources
- CVE List CVE-2012-6035
- NVD CVE-2012-6035
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.