Skip to main content
VulnerabilityPublished Updated

CVE-2025-35973: microcode_ctl security, bug fix, and enhancement update

Affects microcode_ctlSource GCVE Database

0
Compare
Authoritative record:CVE-2025-35973· Medium 4.5

Not known to be exploited · CVSS 4.5 Medium : upgrade to 4:20260812-1.el9 when convenient.

Data as of 16 Nov 2026, 19:49 UTC

CVSS 4.0 base score
4.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4:20260812-1.el9
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Upgrade the AlmaLinux microcode_ctl package to 4:20260812-1.el9.

Affected software

ProductAffectedFixed in
AlmaLinux 9microcode_ctlAffected
  • <4:20260812-1.el9
Fixed in
  • 4:20260812-1.el9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in microcode_ctl version 4:20260812-1.el9 and later. Red Hat recommends applying the latest CPU microcode or system firmware updates provided by hardware manufacturers, such as Intel's microcode updates referenced in Intel Security Advisory INTEL-SA-01428. There is no code-level fix in Red Hat software components; remediation must be done at the processor firmware level. Users should follow vendor guidance to update microcode to mitigate this vulnerability.

Description

CVE-2025-35973 is a privilege escalation vulnerability in Intel processors affecting the kernel hypervisor layer. It arises from improper handling of internal processor values in Ring 0, allowing a local attacker with existing privileged access to escalate privileges. This can impact confidentiality and integrity, particularly in environments using hypervisor-based workload isolation such as Red Hat OpenShift sandboxed containers. The vulnerability requires local privileged access and a high degree of attack complexity. A microcode update addressing this issue is available.

References

Community reviews

Loading reviews…