# Secure boot issues fixed in upstream with shim 15.5 Rocky 8.6 still has shim 15.4

**URL:** <https://forums.rockylinux.org/t/secure-boot-issues-fixed-in-upstream-with-shim-15-5-rocky-8-6-still-has-shim-15-4/6286>\
**Category:** Rocky Linux Help & Support\
**Created:** [June 8, 2022, 7:02pm UTC](https://forums.rockylinux.org/t/secure-boot-issues-fixed-in-upstream-with-shim-15-5-rocky-8-6-still-has-shim-15-4/6286 "2022-06-08T19:02:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![simple\_user](https://avatars.discourse-cdn.com/v4/letter/s/9fc348/32.png) [@simple\_user](https://forums.rockylinux.org/u/simple_user)\
**Post date:** [June 8, 2022, 7:02pm UTC](https://forums.rockylinux.org/t/secure-boot-issues-fixed-in-upstream-with-shim-15-5-rocky-8-6-still-has-shim-15-4/6286/1 "2022-06-08T19:02:01Z")

</div>

The upstream 8.6 release included shim version 15.5-2. It looks like that in part addresses some secure boot issues, including things like the inability to sign kernel modules on VMWare instances with secure boot enabled.

Red Hat bug: [https://bugzilla.redhat.com/show\_bug.cgi?format=multiple&id=1970632](https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1970632)

See [Rocky Linux 8.5 Secure Boot Error](https://forums.rockylinux.org/t/rocky-linux-8-5-secure-boot-error/4760)

And [Rocky Linux 8.5 UEFI Secure Boot Key problem on VMware](https://forums.rockylinux.org/t/rocky-linux-8-5-uefi-secure-boot-key-problem-on-vmware/4850)

for users of Rocky Linux affected by this.

I’m still showing shim version 15.4-2 in my Rocky 8.6 updated system. Is that because there is a delay getting the signature in place?

It’s possible I’m missing something. Is there an expected timeframe for shim 15.5 in Rocky Linux?

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [June 9, 2022, 12:22am UTC](https://forums.rockylinux.org/t/secure-boot-issues-fixed-in-upstream-with-shim-15-5-rocky-8-6-still-has-shim-15-4/6286/2 "2022-06-09T00:22:23Z")

</div>

The shim has to be signed by Microsoft. [Shim 15.5 for Rocky Linux 8 "ia32/x64" · Issue #234 · rhboot/shim-review · GitHub](https://github.com/rhboot/shim-review/issues/234)

---

<div class="post-metadata">

**Author:** ![simple\_user](https://avatars.discourse-cdn.com/v4/letter/s/9fc348/32.png) [@simple\_user](https://forums.rockylinux.org/u/simple_user)\
**Post date:** [June 9, 2022, 1:28am UTC](https://forums.rockylinux.org/t/secure-boot-issues-fixed-in-upstream-with-shim-15-5-rocky-8-6-still-has-shim-15-4/6286/3 "2022-06-09T01:28:47Z")

</div>

Perfect! Thanks so much. I hadn’t been able to dine that during my searching.

---

<div class="post-metadata">

**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brian/32/5777_2.png) [@brian](https://forums.rockylinux.org/u/brian)\
**Post date:** [August 25, 2023, 3:47am UTC](https://forums.rockylinux.org/t/secure-boot-issues-fixed-in-upstream-with-shim-15-5-rocky-8-6-still-has-shim-15-4/6286/4 "2023-08-25T03:47:52Z")

</div>