![\"\"](\"https:\/\/icrowdnewswire.com\/wp-content\/uploads\/2020\/06\/4001-logo.png\"){kind=logo}
<\/p>\n<\/p>\n
![\"A](\"https:\/\/cdn.arstechnica.net\/wp-content\/uploads\/2020\/07\/grub2-boot-worm-update-800x450.jpg\")
<\/section>\nEarly this morning, an urgent bug<\/a> showed up at Red Hat’s bugzilla bug tracker—a user discovered that the RHSA_2020:3216 grub2 security update and RHSA-2020:3218 kernel security update rendered an RHEL 8.2 system unbootable. The bug was reported as reproducible on any clean minimal install of Red Hat Enterprise Linux 8.2.<\/p>\n The patches were intended to close a newly discovered vulnerability in the GRUB2 boot manager called BootHole<\/a>. The vulnerability itself left a method for system attackers to potentially install “bootkit” malware on a Linux system despite that system being protected with UEFI Secure Boot.<\/p>\n <\/p>\n Unfortunately, Red Hat’s patch to GRUB2 and the kernel, once applied, are leaving patched systems unbootable. The issue is confirmed to affect RHEL 7.8 and RHEL 8.2, and it may affect RHEL 8.1 and 7.9 as well. RHEL-derivative distribution CentOS is also affected.<\/p>\n Red Hat is currently advising<\/a> users not to apply the GRUB2 security patches (RHSA-2020:3216<\/a> or RHSA-2020:3217<\/a>) until these issues have been resolved. If you administer a RHEL or CentOS system and believe you may have installed these patches, do not reboot your system<\/em>. Downgrade the affected packages using If you’ve already applied the patches and attempted (and failed) to reboot, boot from an RHEL or CentOS DVD in Troubleshooting mode, set up the network<\/a>, then perform the same steps outlined above in order to restore functionality to your system.<\/p>\n Although the bug was first reported in Red Hat Enterprise Linux, apparently related bug reports are rolling in from other distributions from different families as well. Ubuntu and Debian users are reporting<\/a> systems which cannot boot after installing GRUB2 updates, and Canonical has issued an advisory including instructions<\/a> for recovery on affected systems.<\/p>\n Although the impact of the GRUB2 bug is similar, the scope may be different from distribution to distribution; so far it appears the Debian\/Ubuntu GRUB2 bug is only affecting<\/a> systems which boot in BIOS (not UEFI) mode. A fix has already been committed to Ubuntu’s For Debian users, the fix<\/a> is available in newly committed package We do not have any word at this time about flaws in or impact of GRUB2 BootHole patches on other distributions such as Arch, Gentoo, or Clear Linux.<\/p>\n<\/section>\n Tags:<\/b> JIM SALTER <\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"RHEL and CentOS<\/h2>\n
sudo yum downgrade shim\\* grub2\\* mokutil<\/code> and configure yum<\/code> not to upgrade those packages by temporarily adding exclude=grub2* shim* mokutil<\/code> to \/etc\/yum.conf<\/code>.<\/p>\nOther distributions<\/h2>\n
proposed<\/code> repository, tested, and released to its updates<\/code> repository. The updated and released packages, grub2 (2.02~beta2-36ubuntu3.27) xenial<\/code> and grub2 (2.04-1ubuntu26.2) focal<\/code>, should resolve the problem for Ubuntu users.<\/p>\ngrub2 (2.02+dfsg1-20+deb10u2)<\/code>.<\/p>\nSee Campaign: <\/strong>https:\/\/arstechnica.com\/information-technology\/2020\/07\/new-flaw-neuters-secure-boot-but-theres-no-reason-to-panic-heres-why\/<\/a>
Contact Information:<\/b>
JIM SALTER <\/p>\n
<\/a>, Wire<\/a>, United States<\/a>, English<\/a><\/p>\n<\/div>\n
\nContact Information:<\/h3>\n
Well, you can’t be vulnerable to BootHole if you can’t boot your system. Early this morning, an urgent bug showed up at Red Hat’s bugzilla bug tracker—a user discovered that the RHSA_2020:3216 grub2 security update and RHSA-2020:3218 kernel security update rendered an RHEL 8.2 system unbootable. The bug was reported as reproducible on any clean minimal install … Continue reading Red Hat and CentOS systems aren’t booting due to BootHole patches<\/span><\/a> Continue Reading