Security readout for executives and security teams
Plain-English summary
Certain Intel Xeon 6 systems using Intel TDX may expose protected data to an authenticated local user. Exploitation requires high complexity, specific conditions, and special internal knowledge. The primary concern is confidentiality across a system boundary; the supplied evidence indicates no direct integrity or availability impact.
Executive priority
Treat this as a targeted, moderate-priority confidentiality issue. Promptly identify TDX-enabled Xeon 6 deployments, especially systems processing sensitive or multi-tenant workloads. Escalate priority where untrusted users receive local access. Broad emergency action is not supported by the supplied exploitation evidence.
Technical view
CVE-2025-31938 is an insufficiently granular access-control weakness, classified as CWE-1220, in an unspecified subsystem of some Intel Xeon 6 Scalable processors with TDX. The CVSS 4.0 vector requires local access, low privileges, high complexity, and additional attack requirements. Successful exploitation could cause high subsequent-system confidentiality impact without user interaction.
Likely exposure
Potential exposure is limited to Intel Xeon 6 Scalable systems using TDX that Intel identifies as affected. Exact processor versions, steppings, firmware levels, and configurations are absent from the supplied record. Multi-tenant or confidential-computing environments warrant particular review because the stated consequence crosses a system confidentiality boundary.
Exploitation context
The attacker must already be an authenticated user with local access. Exploitation is described as highly complex, conditional, and dependent on special internal knowledge. The bundle marks the CVE as not present in KEV and provides no evidence of active exploitation or a publicly available exploit.
Researcher notes
The record does not identify the vulnerable subsystem or enumerate affected versions. Its CVSS 4.0 vector reports no direct vulnerable-system confidentiality impact but high subsequent-system confidentiality impact. Validation should therefore focus on Intel's affected-product matrix and trust-boundary consequences rather than assuming every Xeon 6 or TDX deployment is vulnerable.
Mitigation direction
- Review Intel advisory INTEL-SA-01404 for affected processor and platform details.
- Inventory Xeon 6 systems and determine where Intel TDX is enabled or available.
- Apply the remediation Intel specifies after confirming platform applicability.
- Restrict local authenticated access and strengthen tenant separation until remediation is confirmed.
Validation and detection
- Record processor model, stepping, firmware level, and TDX enablement for each system.
- Compare collected system details with Intel advisory INTEL-SA-01404.
- Review which users or tenants can obtain authenticated local access.
- After remediation, verify systems match Intel's required version or configuration.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-1220: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-31938 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N——intelVulnerability scoring details
Base CVSS 4.0 score
4.3MediumVector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01404.htmlCVE reference, intel
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Granularity of Access Control
Insufficient Granularity of Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.