Bug 1861857 - grub2 should get resynced with 7.8 branch
Summary: grub2 should get resynced with 7.8 branch
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grub2
Version: 7.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
Depends On: 1861858 1861860 1861861
TreeView+ depends on / blocked
Reported: 2020-07-29 18:03 UTC by Ray Strode [halfline]
Modified: 2022-07-09 11:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1861855
Last Closed: 2020-08-03 11:53:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3271 0 None None None 2020-08-03 11:53:06 UTC

Description Ray Strode [halfline] 2020-07-29 18:03:11 UTC
+++ This bug was initially created as a clone of Bug #1861855 +++

As part of the fixes for CVE-2020-10713 grub needs to be resynced with the 7.8 branch.

This bug is to track that resync.

Comment 2 Ray Strode [halfline] 2020-07-29 18:09:52 UTC
The resync brings in these fixes:

bug 1446418: grub2 efidisk identifying cd/dvd drive as hd
bug 1496952: grub2-efi-x64 and shim-x64 packages will always fail rpm --verify if /boot/efi is mounted
bug 1497918: /boot/grub2/grubenv is changed into a dead symlink by installing grub2-efi package on non-uefi machine
bug 1614259: grub2 should depend on  /usr/lib/libc.so instead of glibc32, causes rpmbuild --rebuild to fail
bug 1616395: grub2 doesn't handle relative paths correctly for UEFI HTTP Boot
bug 1732765: UEFI HTTP boot over IPv6 does not work
bug 1748019: Broken upgrade for non-intel arches beause of wrong efi provides

Comment 9 errata-xmlrpc 2020-08-03 11:53:03 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.


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