CVE-2025-35973: Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal O...
Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal OS may allow an escalation of privilege. Authorized adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and require no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.
Security readout for executives and security teams
Plain-English summary
This Intel processor issue could let an already highly privileged local user gain greater control over an affected system. Exploitation is difficult, requires specific conditions and internal knowledge, and needs no user interaction. Successful exploitation could seriously affect downstream confidentiality and integrity, but the supplied evidence indicates no availability impact.
Executive priority
Treat this as a targeted, moderate-priority infrastructure issue. Promptly identify exposed processor models, emphasizing shared virtualization hosts and sensitive platforms. Emergency action is not supported by the supplied evidence, but confirmed affected systems warrant planned remediation because successful privilege escalation could substantially compromise confidentiality and integrity.
Technical view
CVE-2025-35973 is improper value handling in Ring 0 environments, including kernels, hypervisors, and bare-metal operating systems. The CVSS 4.0 score is 4.5. Exploitation requires local access, high privileges, high complexity, and additional attack requirements. The supplied bundle does not identify affected processor models or remediation versions.
Likely exposure
Exposure is limited to Intel processor models listed by Intel as affected and systems where an authorized, highly privileged adversary has local access. Exact affected models and versions are unavailable in the supplied details, so organizations must compare hardware inventories with Intel advisory INTEL-SA-01428.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires privileged local access, high complexity, special internal knowledge, and specific attack conditions. These barriers reduce likelihood but do not eliminate risk in shared, virtualized, or administrator-accessible environments.
Researcher notes
CWE-229 is assigned. CVSS 4.0 is AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N. This indicates limited vulnerable-system impact but high subsequent confidentiality and integrity impact. The bundle provides neither affected model details nor technical root-cause depth, proof-of-concept information, detection indicators, or confirmed patch versions.
Mitigation direction
Review Intel advisory INTEL-SA-01428 for affected processors and vendor-approved remediation.
Apply applicable firmware, microcode, or platform updates only as directed by Intel and system vendors.
Restrict privileged local access until affected systems are assessed and remediated.
Prioritize shared hypervisors and sensitive systems if their processors are confirmed affected.
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-229: 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-229 · source CWE mapping
Improper Handling of Values
Improper Handling of Values represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.