Skip to main content
CVE-2025-24305VulnerabilityPublished Updated

CVE-2025-24305: Intel(R) Xeon(R) processors · Escalation of Privilege

Affects Intel(R) Xeon(R) processorsSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Monitor Intel's official security advisories closely and apply firmware updates or patches for the ACTM firmware as soon as they become available. 2. Restrict local privileged access strictly to trusted personnel and enforce the principle of least privilege to minimize the number of users with high-level access. 3. Implement robust access controls and multi-factor authentication for administrative accounts to reduce the risk of privilege abuse. 4. Employ endpoint detection and response (EDR) solutions capable of monitoring unusual privilege escalation attempts or suspicious activity at the kernel or firmware level. 5. Use hardware-based security features and virtualization-based security to isolate critical workloads and limit the impact of potential privilege escalations. 6. Conduct regular audits of privileged user activities and system logs to detect early signs of exploitation attempts. 7. In environments where patching may be delayed, consider temporary compensating controls such as disabling unnecessary local accounts or restricting physical access to affected systems. 8. Collaborate with hardware vendors and security teams to validate firmware integrity and ensure secure boot processes are enforced.

Description

Insufficient control flow management in the Alias Checking Trusted Module (ACTM) firmware for some Intel(R) Xeon(R) processors may allow a privileged user to potentially enable escalation of privilege via local access.

References

Community reviews

Loading reviews…