CVE-2025-35987 Intel CVE debrief

Who should care

Defenders and administrators of systems using Intel(R) Software Guard Extensions Data Center Attestation Primitives should assess exposure and prioritize verification of the vulnerability's existence and impact on their systems.

Why it matters

Defenders should care about CVE-2025-35987 because it may allow a denial of service and potentially enable data alteration in Intel(R) Software Guard Extensions Data Center Attestation Primitives within Ring 0: Kernel, requiring verification and potential patching or mitigation.

• Verification of vulnerability existence and impact is required
• Potential denial of service and data alteration may occur
• Defenders should prioritize patching or mitigating the vulnerability

Technical summary

The potential vulnerability exists in Intel(R) Software Guard Extensions Data Center Attestation Primitives within Ring 0: Kernel, which may allow a denial of service and potentially enable data alteration by an authorized adversary with a privileged user and high complexity attack. This vulnerability requires verification and potential patching or mitigation, especially for defenders and administrators of systems using Intel(R) Software Guard Extensions Data Center Attestation Primitives. The CVE record and NVD entry provide information on the potential vulnerability, its impact, and affected systems.

Defensive priority

Defenders should prioritize verifying the vulnerability's existence and impact on their systems, especially those using Intel(R) Software Guard Extensions Data Center Attestation Primitives.

Recommended defensive actions

• Verify the vulnerability's existence and impact on your systems
• Check for any available patches or updates from Intel
• Monitor system logs for potential denial of service attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD entry provide information on the potential vulnerability, its impact, and affected systems. However, the corpus does not establish versions, exploitation, impact, or remediation, requiring verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.