Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

This is seen on HPE hardware with shim-x64 of RHEL7. It appears that shim loops indefinitely trying to mirror the next certificate due to lacking space to store it, verbose mode shows the loop happens on the following excerpt:
~~~
mok.c:231:get_max_var_sz() max_var_sz:9C remaining_sz:D8 max_storage_sz:FFE4^M
mok.c:425:mirror_mok_db() esd:0x9E56EF04 adj:0x0^M
mok.c:367:mirror_mok_db() pos:0x4EEC FullDataSize:0x54DD^M
mok.c:383:mirror_mok_db() esl[4] 0x9E56EEE8 = {sls=0x60D, ss=0x5F1} esd:0x9E56EF04^M
 :
~~~

We confirmed that shim-x64 of RHEL8 is not having this issue due to having commit https://github.com/rhboot/shim/commit/f9294c2fa9feaf5353c0b7a4a7ce102a820c1a3f

Please backport this commit asap.


Version-Release number of selected component (if applicable):

shim-15-11


How reproducible:

Always on some HPE hardware (ProLiant XL230k Gen10 with BIOS 2.42, Firmware Revision 2.44)

Additional info:

This is quite critical since we cannot tell the customers to install the shim from RHEL8 for now: the shim works, but I doubt mokutil of RHEL7 will be compatible.

Hi,
We have a build that is available for testing: https://people.redhat.com/mlewando/shim-signed-15.6-1.el7_9/
We will do sanity testing, and if HPE is able and willing to test, that would be great.
thank you!

Tested on x86 VM: installed RHEL-7.9-updates-20221122.0 Server and updated shim to shim-x64-15.6-1.el7_9.x86_64
VM was able to boot with SB enabled and disabled

RHEL-7.9 on aarch is not supported, so not testing.

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 (shim bug fix and enhancement update), 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-2023:1991

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days