LiveActive security incident?Get immediate response
CVE Record

CVE-2012-6035: The do_tmem_destroy_pool function in the Transcendent Memory (TMEM) in Xen 4.0, 4.1, and 4.2 does not prope...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A user inside a Xen guest could trigger a flaw in Xen's TMEM handling and potentially crash the host. The CVE description also states arbitrary code execution is possible, but the public bundle does not provide details. This matters most for older Xen 4.0, 4.1, and 4.2 environments, especially where guests are not fully trusted. Exposure is likely limited to legacy Xen 4.0, 4.1, and 4.2 hosts with TMEM functionality present. The relevant attacker position is inside a guest OS, so shared hosting, multi-tenant virtualization, and environments with untrusted guest administrators carry the most concern. Treat this as a high-priority legacy virtualization risk if older Xen hosts remain in use. A guest-to-host crash or code execution issue can affect multiple workloads on the same physical server. If the organization no longer uses Xen 4.0 through 4.2, priority drops to inventory confirmation. Mitigation focus: Inventory Xen hosts and identify versions 4.0, 4.1, and 4.2.; Review Xen XSA-15 and vendor advisories for fixed packages or supported mitigations.; Apply vendor security updates where available for affected Xen installations..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2012-6035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.