LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 4.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.

Validation and detection

  • Inventory Intel processor models, platform firmware, microcode, operating systems, and hypervisors.
  • Compare inventory details against the affected-product table in INTEL-SA-01428.
  • Confirm required updates with hardware, operating-system, and hypervisor vendors.
  • Verify deployed firmware or microcode versions after remediation using approved inventory tooling.
  • Monitor Intel guidance for revisions because affected versions are not specified in the supplied bundle.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-35973 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.5 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4.5CVSS 4.0MediumCVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:Nintel

Vulnerability scoring details

Base CVSS 4.0 score

4.5Medium
CVSS 4.0 vector shape for CVE-2025-35973Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aIntel(R) ProcessorsSee referencesunaffected
Weakness

CWE details

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.