CVE-2024-28956VulnerabilityPublished 1 Jul 2025Updated 5 Nov 2026

Red Hat Security Advisory: microcode_ctl security update

Affects Red Hat microcode_ctlSource GCVE Database

Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 5 Nov 2026, 17:03 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released updated microcode_ctl packages for Red Hat Enterprise Linux 9.4 Extended Update Support and related variants. Users should apply these official updates as described in the Red Hat advisory (https://access.redhat.com/articles/11258) to remediate the vulnerabilities. Since the update is available, applying the patch is the recommended mitigation. No additional or alternative mitigations are indicated by the vendor.

Description

Red Hat has issued a security advisory for the microcode_ctl package, which provides microcode updates for Intel and AMD processors. The update addresses multiple vulnerabilities identified by CVE identifiers including CVE-2024-28956, CVE-2025-24495, and CVE-2025-20012. The advisory rates the security impact as moderate and applies to Red Hat Enterprise Linux 9.4 Extended Update Support and related variants. Users are advised to apply the provided updates to mitigate these issues.

Reports on CVE-2024-28956

GCP-2025-024GCP Compute Engine Security2026-10-26

Impact

The vulnerabilities affect the microcode update mechanism for Intel and AMD processors on Red Hat Enterprise Linux 9.4 Extended Update Support and related variants. The security impact is rated moderate by Red Hat. Specific impacts are not detailed in the advisory, and no known exploits in the wild have been reported. The vulnerabilities could potentially allow attackers to affect processor microcode, but exact exploitation details are not provided.

CWE-1421Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution (opens in a new tab)
Base weakness
A processor event may allow transient operations to access architecturally restricted data (for example, in another address space) in a shared microarchitectural structure (for example, a CPU cache), potentially exposing the data over a covert channel.
Architecture and Design
Hardware designers may choose to engineer the processor's pipeline to prevent architecturally restricted data from being used by operations that can execute transiently.
Architecture and Design
Hardware designers may choose not to share microarchitectural resources that can contain sensitive data, such as fill buffers and store buffers.
Architecture and Design
Hardware designers may choose to sanitize specific microarchitectural state (for example, store buffers) when the processor transitions to a different context, such as whenever a system call is invoked.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1423Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution (opens in a new tab)
Base weakness
Shared microarchitectural predictor state may allow code to influence transient execution across a hardware boundary, potentially exposing data that is accessible beyond the boundary over a covert channel.
Architecture and Design
The hardware designer can attempt to prevent transient execution from causing observable discrepancies in specific covert channels.
Architecture and Design
Hardware designers may choose to use microarchitectural bits to tag predictor entries. For example, each predictor entry may be tagged with a kernel-mode bit which, when set, indicates that the predictor entry was created in kernel mode.
Architecture and Design
Hardware designers may choose to sanitize microarchitectural predictor state (for example, branch prediction history) when the processor transitions to a different context, for example, whenever a system call is invoked.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-696Incorrect Behavior Order (opens in a new tab)
Class weakness
The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
Attack patterns
Padding Oracle Crypto Attack (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1419Incorrect Initialization of Resource (opens in a new tab)
Class weakness
The product attempts to initialize a resource but does not correctly do so, which might leave the resource in an unexpected, incorrect, or insecure state when it is accessed.
Implementation
Choose the safest-possible initialization for security-related resources.
Implementation
Ensure that each resource (whether variable, memory buffer, register, etc.) is fully initialized.
Implementation
Pay close attention to complex conditionals or reset sources that affect initialization, since some paths might not perform the initialization.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

Reports on CVE-2024-28956

AI analysisMachine-generated, updated 5 Nov 2026, 17:03 UTC

WeaknessesCWE-1421, CWE-1423, CWE-696 +1

Technical details

References

Community reviews

Related threats