CVE-2025-35987: Omission of security-relevant information for some Intel(R) Software Guard Extensions Data Center Attestati...
Omission of security-relevant information for some Intel(R) Software Guard Extensions Data Center Attestation Primitives within Ring 0: Kernel may allow a denial of service. Authorized adversary with a privileged user combined with a high complexity attack may enable data alteration. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (low) impacts.
Security readout for executives and security teams
Plain-English summary
A flaw in Intel Software Guard Extensions Data Center Attestation Primitives could let an already privileged local user disrupt service or alter limited data. Exploitation requires high complexity, specific prerequisites, and specialized internal knowledge. The reported direct impact is limited, although subsequent integrity impact could be high.
Executive priority
Treat this as a targeted remediation item for environments using Intel SGX DCAP, not an organization-wide emergency. Prioritize internet-facing or sensitive workloads where local privileged access could be obtained through another compromise. Confirm exposure promptly because exact affected versions are absent from the supplied CVE record.
Technical view
CVE-2025-35987 is a CWE-223 omission of security-relevant information affecting certain Intel SGX Data Center Attestation Primitives within Ring 0: Kernel. It is rated CVSS 4.0 4.3. The vector indicates local access, high privileges, high complexity, attack prerequisites, and no user interaction, with limited direct integrity and availability effects.
Likely exposure
Exposure is limited to systems using affected Intel SGX Data Center Attestation Primitives Ring 0: Kernel versions. Exact affected versions are not included in the supplied record and must be determined from Intel advisory INTEL-SA-01421. Systems without this component are not shown to be exposed.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as a KEV entry. A successful attack requires an authorized, highly privileged adversary with local access, special internal knowledge, high complexity, and additional attack prerequisites. No user interaction is required.
Researcher notes
The primary weakness classification is CWE-223. The CVSS vector reports no direct confidentiality impact, low direct integrity and availability impact, and high subsequent-system integrity impact. The source bundle does not explain the omitted information, affected version boundaries, technical root cause, patch details, or observed exploitation; consult Intel's advisory for those specifics.
Mitigation direction
Review Intel advisory INTEL-SA-01421 for affected versions and vendor-provided remediation.
Apply Intel-recommended updates or mitigations after confirming component and version applicability.
Restrict privileged local access to systems running affected SGX DCAP components.
Monitor privileged activity and unexpected integrity or availability changes on exposed systems.
Validation and detection
Inventory systems using Intel SGX Data Center Attestation Primitives Ring 0: Kernel.
Compare installed component versions with the affected versions listed in Intel's advisory.
Confirm whether privileged local access is limited to approved administrators and service accounts.
Verify Intel-recommended updates or mitigations are applied and recorded.
Review monitoring data for unexplained data changes, kernel faults, or service disruption.
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.
cwe · low confidence lookup
CWE-223: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-223 · source CWE mapping
Omission of Security-relevant Information
Omission of Security-relevant Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.