
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2025-31648 is an improper handling of values vulnerability (CWE-229) in the microcode flow for certain Intel Processor families that may allow escalation of privilege. It was disclosed on February 10, 2026, via Intel's security advisory INTEL-SA-01396. The vulnerability requires local access, high attack complexity, and a privileged user (startup code and SMM adversary), with no user interaction needed. It carries a CVSS v3.1 base score of 3.9 (Medium) and a CVSS v4.0 base score of 1.8 (Low) (Intel Advisory).
The root cause is classified as CWE-229 (Improper Handling of Values) within the microcode execution flow of affected Intel processor families. Exploitation requires a privileged attacker (e.g., one with access to startup code or System Management Mode) with special internal knowledge of the processor's microcode behavior, combined with high attack complexity conditions. The attack vector is local, the scope is changed (indicating impact beyond the vulnerable component), and successful exploitation yields low confidentiality and low integrity impacts with no availability impact. No public technical write-ups or proof-of-concept code have been identified (Intel Advisory).
Successful exploitation could result in limited escalation of privilege, with low confidentiality and low integrity impacts on both the vulnerable system and subsequent systems within scope. Because the scope is changed, an attacker operating within a privileged context (such as SMM) could potentially affect security boundaries beyond the initially compromised component. Availability is not impacted. The real-world risk is constrained by the high complexity and privileged access requirements (Intel Advisory).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported for CVE-2025-31648. The EPSS score is extremely low at 0.004%, reflecting the very limited likelihood of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires a highly privileged local attacker with special internal knowledge of Intel microcode internals and high attack complexity, significantly limiting practical exploitability (Intel Advisory).
Intel has released updated microcode to address this vulnerability, documented in advisory INTEL-SA-01396 published February 10, 2026. Affected users should apply the latest Intel microcode updates provided by their system or OS vendor. Multiple vendors have issued corresponding advisories and patches, including Lenovo (PS500804), HPE (hpesbhf05008en_us, hpesbhf05016en_us), Dell (DSA-2026-010, DSA-2026-186, DSA-2026-188), Ubuntu (USN-8068-1), Amazon Linux (ALAS2-2026-3294, ALAS2023-2026-1675), and Mageia (MGASA-2026-0043). Prioritize applying microcode updates on systems where privileged local access (especially SMM-level) is a concern (Intel Advisory, Lenovo Advisory, HPE Advisory).
The vulnerability received routine coverage from Linux distribution security teams and hardware vendors, with advisories issued by Lenovo, HPE, Dell, Ubuntu, Amazon Linux, Mageia, SUSE, and XCP-ng as part of coordinated microcode update rollouts. Coverage in the broader security community has been limited, consistent with the low CVSS score and high exploitation complexity. No notable researcher commentary or significant social media discussion has been identified beyond standard patch notification channels.
Fix availability across major Linux distributions and their releases.
bookworm
intel-microcode
sid
intel-microcode: 3.20260210.1
trixie
intel-microcode
RHEL 8
microcode_ctl.src
RHEL 9
microcode_ctl.src
RHEL 10
microcode_ctl.src
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."