CVE-2012-6030

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2012-11-23 20:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:47 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 7.2 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2012-11-23 20:55 UTC

Last modified

2026-06-16 23:47 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-20 · Improper input validation

Record status

Modified

Affected

• Xen 4.0.0
• Xen 4.1.0
• Xen 4.2.0

Attack profile CVSS 2.0 · 7.2

Attack vector

Local

Complexity

Low

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-6030.md and follow it. Check whether this project is affected by CVE-2012-6030. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge