CVE-2013-2076: n/a vulnerability

CVE-2013-2076: Xen 4.0.x, 4.1.x, and 4.2.x, when running on AMD64 processors, only save/restore the FOP, FIP, and FDP x87...

Xen 4.0.x, 4.1.x, and 4.2.x, when running on AMD64 processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one domain to determine portions of the state of floating point instructions of other domains, which can be leveraged to obtain sensitive information such as cryptographic keys, a similar vulnerability to CVE-2006-1056. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 15:27 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2013-2076 is an information leak in Xen on AMD64 systems. A guest domain may infer parts of another domain’s floating-point instruction state, potentially including sensitive material such as cryptographic keys. This mainly matters for organizations still running old Xen 4.0.x, 4.1.x, or 4.2.x on affected AMD64 hardware. Exposure is likely limited to legacy Xen deployments: versions 4.0.x, 4.1.x, and 4.2.x running on AMD64 processors, especially XSAVE/XRSTOR-capable AMD CPUs. Modern supported Xen environments are less likely exposed, but should be verified against vendor advisories. Medium priority unless legacy Xen on AMD64 is still in production. For cloud, hosting, or multi-tenant virtualization, treat as higher urgency because the issue crosses guest isolation boundaries. If no such Xen estate exists, business exposure is likely low. Mitigation focus: Identify any Xen 4.0.x, 4.1.x, or 4.2.x hosts on AMD64 hardware.; Apply relevant Xen or distribution security updates from vendor advisories.; Prioritize upgrades for unsupported Xen versions and legacy host operating systems..

Prepared: Jun 14, 2026, 16:16 UTC (UTC+00:00)

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.

cve · low confidence lookup

CVE-2013-2076 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: Aug 28, 2013, 17:00 UTC (UTC+00:00)

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

1Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5

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.