Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1585939 - include AMD CPUID 0x00610f01 in RHEL-7 linux-firmware [rhel-7.5.z]
include AMD CPUID 0x00610f01 in RHEL-7 linux-firmware [rhel-7.5.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: linux-firmware (Show other bugs)
7.6
Unspecified Unspecified
high Severity urgent
: rc
: ---
Assigned To: Bruno Meneguele
Rachel Sibley
: ZStream
Depends On: 1583720
Blocks:
  Show dependency treegraph
 
Reported: 2018-06-05 03:11 EDT by Oneata Mircea Teodor
Modified: 2018-06-18 05:28 EDT (History)
7 users (show)

See Also:
Fixed In Version: linux-firmware-20180220-62.2.git6d51311.el7_5
Doc Type: Bug Fix
Doc Text:
A previous update to the linux-firmware packages that added new capabilities to enhance mitigation of CVE-2017-5715 (the Spectre variant 2 vulnerability) introduced a regression when it inadvertently removed support for AMD CPUID 0x00610f01. As a consequence, the kernel would be unable to update the microcode loaded by BIOS or UEFI if it was outdated because the loaded microcode version is dependent on the BIOS or UEFI version in use. This update restores microcode support for the mentioned CPU family, and the microcode can be correctly updated again.
Story Points: ---
Clone Of: 1583720
Environment:
Last Closed: 2018-06-12 12:11:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1838 None None None 2018-06-12 12:11 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-06-05 03:11:37 EDT
This bug has been copied from bug #1583720 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 7 errata-xmlrpc 2018-06-12 12:11:13 EDT
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:1838

Note You need to log in before you can comment on or make changes to this bug.