microcode_ctl: The microcode_ctl packages provide microcode updates for Intel and AMD processors. Security Fix(es): * microcode_ct...
CVE-2024-28047 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2024-28047, released February 12, 2025. It is not reported as exploited. Patch Radar priority: Routine.
The microcode_ctl packages provide microcode updates for Intel and AMD processors. Security Fix(es): * microcode_ctl: Improper input validation in UEFI firmware (CVE-2024-28047) * microcode_ctl: Insufficient granularity of access control in UEFI firmware (CVE-2024-39279) * microcode_ctl: mproper initialization in UEFI firmware OutOfBandXML module (CVE-2024-31157) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Additional Changes: For detailed information on changes in this release, see the Red Hat Enterprise Linux 9 Release Notes linked from the References section.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| intel-microcode · Debian 12.15 (bookworm) | 3.20250211.1~deb12u1 | DEBIAN-CVE-2024-28047 | Feb 12, 2025 |
| intel-microcode · Debian 13.5 (trixie) | 3.20250211.1 | DEBIAN-CVE-2024-28047 | Feb 12, 2025 |
| intel-microcode · Debian 14 | 3.20250211.1 | DEBIAN-CVE-2024-28047 | Feb 12, 2025 |
| microcode_ctl · RHEL 8 | 4:20250211-1.el8_10 | RHEA-2025:3114 | Mar 24, 2025 |
| microcode_ctl · RHEL 9 | 4:20250211-1.el9_6 | RHSA-2025:7043 | May 13, 2025 |
| microcode_ctl · almalinux 9 | 4:20250211-1.el9_6 | ALSA-2025:7043 | May 13, 2025 |
| microcode_ctl · ol 9 | 4:20250211-1.0.1.el9_6 | ELSA-2025-7043 | May 16, 2025 |
| microcode_ctl · rocky 9 | 4:20250211-1.el9_6 | RLSA-2025:7043 | Oct 4, 2025 |
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.