LiveActive security incident?Get immediate response
CVE Record

CVE-2006-7215: The Intel Core 2 Extreme processor X6800 and Core 2 Duo desktop processor E6000 and E4000 incorrectly set t...

The Intel Core 2 Extreme processor X6800 and Core 2 Duo desktop processor E6000 and E4000 incorrectly set the memory page Access (A) bit for a page in certain circumstances involving proximity of the code segment limit to the end of a code page, which has unknown impact and attack vectors on certain operating systems other than OpenBSD, aka AI90.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a legacy Intel Core 2 processor erratum where specific CPUs can incorrectly mark a memory page as accessed. The CVE record says the real-world impact and attack paths are unknown, except that OpenBSD was specifically discussed in the original disclosure context. Treat this mainly as legacy hardware risk unless affected systems still run sensitive workloads. Exposure is likely limited to organizations still operating legacy Core 2 Extreme X6800 or Core 2 Duo E6000/E4000 desktop-class systems, especially where old operating systems or unmaintained firmware remain in use. Modern fleets are unlikely to be exposed unless legacy hardware remains in labs, industrial systems, kiosks, or archives. Prioritize as a legacy asset-management issue, not an emergency, unless affected processors still support sensitive, multi-user, or business-critical environments. The main decision is whether to retire or isolate old hardware where vendor support and reliable mitigation evidence are limited. Mitigation focus: Inventory systems for Intel Core 2 Extreme X6800 and Core 2 Duo E6000/E4000 processors.; Check Intel processor specification updates and OEM BIOS or microcode guidance for affected hardware.; Review operating-system vendor advisories for handling of this CPU erratum..

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.

cve · low confidence lookup

CVE-2006-7215 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
1Source 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.