Linux ·
Rocky Linux · Security advisory · July 29, 2025
Rocky Linux · Security advisory · July 29, 2025RLSA-2025:10991: microcode_ctl security update
RLSA-2025:10991, released July 29, 2025, fixes 6 CVEs in microcode_ctl (version 4:20250512-1.el8_10). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
7.8
Base score, 0 to 10
Highest EPSS
0.0043
37th percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 1
Routine 5
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| microcode_ctl | rocky 8 | 4:20250512-1.el8_10 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2024-28956 | kernel-64kb: x86/ibt: Keep IBT disabled during alternative patching (bsc#1242006). | 7.8 | 0.0043 | None reported |
| Routine | CVE-2024-45332 | ucode-intel: Exposure of sensitive information caused by shared microarchitectural predictor state that influences transient execu... | 5.6 | 0.0027 | None reported |
| Routine | CVE-2025-20012 | ucode-intel: Incorrect behavior order for some Intel Core Ultra Processors may allow an unauthenticated user to potentially enable... | 5.6 | 0.0026 | None reported |
| Routine | CVE-2025-20623 | ucode-intel: Exposure of sensitive information caused by shared microarchitectural predictor state that influences transient execu... | 5.6 | 0.0020 | None reported |
| Routine | CVE-2024-43420 | ucode-intel: Exposure of sensitive information caused by shared microarchitectural predictor state that influences transient execu... | 5.6 | 0.0020 | None reported |
| Routine | CVE-2025-24495 | ucode-intel: Incorrect initialization of resource in the branch prediction unit for some Intel Core Ultra Processors may allow an... | 5.6 | 0.0019 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.