Bug 1527310 - Microcode on AMD family 16h processors not updated early in the boot process [rhel-7.2.z]
Summary: Microcode on AMD family 16h processors not updated early in the boot process ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.3
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
Marie Hornickova
URL:
Whiteboard:
: 1529310 (view as bug list)
Depends On: 1476039
Blocks: CVE-2017-5715
TreeView+ depends on / blocked
 
Reported: 2017-12-19 07:45 UTC by Oneata Mircea Teodor
Modified: 2018-01-08 16:29 UTC (History)
15 users (show)

Fixed In Version: dracut-033-360.el7_2.3
Doc Type: Bug Fix
Doc Text:
Previously, the dracut tool incorrectly copied the AMD family 15h microcode into the Initial RAM File System (initramfs) on systems with AMD family 16h processors. Consequently, the microcode on such systems was not updated early enough in the boot process. This update fixes dracut to copy the correct AMD family 16h microcode into initramfs, and the microcode is now correctly updated in the early phase of the boot process.
Clone Of: 1476039
Environment:
Last Closed: 2018-01-08 16:29:28 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0062 0 normal SHIPPED_LIVE dracut bug fix update 2018-01-08 21:26:21 UTC

Description Oneata Mircea Teodor 2017-12-19 07:45:58 UTC 
This bug has been copied from bug #1476039 and has been proposed to be backported to 7.2 z-stream (EUS).
Comment 4 Lukáš Nykrýn 2018-01-04 10:30:01 UTC 
*** Bug 1529310 has been marked as a duplicate of this bug. ***
Comment 5 Jan Stodola 2018-01-04 12:15:35 UTC 
Reproduced on RHEL-7.2 GA
Verified with dracut-033-360.el7_2.3, the correct microcode was included in the early CPIO image depending on the CPU family.

Moving to VERIFIED.
Comment 8 errata-xmlrpc 2018-01-08 16:29:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0062
Note You need to log in before you can comment on or make changes to this bug.