[Bug 1209985] New: Secure boot violation
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 Bug ID: 1209985 Summary: Secure boot violation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: nwr10cst-oslnx@yahoo.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: Booting today, I got a message: Something has gone wrong. Security violation. It mentioned "shim", so I assume it was problem with validating "shim.efi". The message goes past very quickly, so it is hard to get the exact wording. After that it shuts the system down. Microsoft Windows 8.1 still boots normally. However, I get this failure with both the Tumbleweed/openSUSE shim and with Leap/SUSE shim. Earlier today, I booted to Tumbleweed. That boot used the shim from Leap 15.4. I then updated Tumbleweed (previous update was 2 weeks earlier). On rebooting after that update, I ran into this problem. I'm suspecting that something happened during the update to cause this -- perhaps NVRAM corruption. But that's only a guess. Disabling secure-boot allows me to use the system again. Looking at various keys with "mokutil", I cannot see anything with a date that expires today. The problem might be hardware dependent. Secure-boot works as expected in a KVM virtual machine. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c1 --- Comment #1 from Carlos Gonzalez <piteccelaya@gmail.com> --- Can confirm that this also happens on openSUSE Leap 15.4 with all latest updates as of this current hour, including kernel and grub updates. Laptop is Acer Aspire 3 A315-58 released on 2021. Reproducible: Always (unless disabling secure boot in BIOS settings) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c2 Carlos Gonzalez <piteccelaya@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |piteccelaya@gmail.com --- Comment #2 from Carlos Gonzalez <piteccelaya@gmail.com> --- Exact error message: Verifying shim SBAT data failed: Security Policy Violation Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation Which appears right after BIOS's splash pic, but does not allow Grub to boot, and instead self shuts down immediately. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c3 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #3 from Andrei Borzenkov <arvidjaar@gmail.com> --- (In reply to Carlos Gonzalez from comment #2)
Exact error message:
Verifying shim SBAT data failed: Security Policy Violation Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation
Which appears right after BIOS's splash pic, but does not allow Grub to boot, and instead self shuts down immediately.
Are you using multiboot? What openSUSE or other distributions are used? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c4 --- Comment #4 from Andrei Borzenkov <arvidjaar@gmail.com> --- There could be a problem in mixed environment. After booting the current Leap 15.4 shim (shim-15.7-150300.4.11.1.x86_64) the SbatLevel is set to bor@10:~> sudo cat /sys/firmware/efi/vars/SbatLevelRT-605dab50-e046-4300-abb6-3dd810dd8b23/data sbat,1,2022111500 shim,2 grub,3 bor@10:~> objcopy -j .sbat -O binary /usr/lib64/efi/shim.efi /dev/stdout sbat,1,SBAT Version,sbat,1,https://github.com/rhboot/shim/blob/main/SBAT.md shim,3,UEFI shim,shim,1,https://github.com/rhboot/shim shim.sle,1,SUSE Linux Enterprise,shim,15.7,mail:security@suse.de bor@10:~> Leap 15.4 shim has version 3 so it will pass verification. But Tumbleweed shim remains on version 1 user@uefi:~> objcopy -O binary -j .sbat /usr/share/efi/x86_64/shim.efi /dev/stdout sbat,1,SBAT Version,sbat,1,https://github.com/rhboot/shim/blob/main/SBAT.md shim,1,UEFI shim,shim,1,https://github.com/rhboot/shim shim.opensuse,1,The openSUSE project,shim,15.4,mail:security-team@suse.de user@uefi:~> Tumbleweed shim should not reset SbatLevel due to earlier date user@uefi:~> cat /sys/firmware/efi/efivars/SbatLevelRT-605dab50-e046-4300-abb6-3dd810dd8b23 sbat,1,2021030218 user@uefi:~> and so will fail self-verification according to configured policy. (In reply to Neil Rickert from comment #0)
Earlier today, I booted to Tumbleweed. That boot used the shim from Leap 15.4. I then updated Tumbleweed (previous update was 2 weeks earlier). On rebooting after that update, I ran into this problem. I'm suspecting that something happened during the update to cause this -- perhaps NVRAM corruption. But that's only a guess.
Disabling secure-boot allows me to use the system again.
Neil, could you please Show the current value of SbatLevelRT EFI variable 1. Make sure you are using Tumbleweed shim for booting 2. run on Tumbleweed mokutil --set-sbat-policy reset while secure boot is disabled. Then reboot. 3. If you will see MokManager requesting to confirm, do it. 4. Enable Secure Boot 5. Reboot again You should be able to boot into Tumbleweed. Check value of SbatLevelRT again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c5 --- Comment #5 from hui <sturm-fr@web.de> --- It seems it is related to this change: https://bugzilla.suse.com/show_bug.cgi?id=CVE-2022-28737 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c6 --- Comment #6 from Andrei Borzenkov <arvidjaar@gmail.com> --- (In reply to Andrei Borzenkov from comment #4)
mokutil --set-sbat-policy reset
Sorry, it is "delete", not "reset". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c7 --- Comment #7 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Responding to c#5 Yes, that change looks to be the likely culprit. As a result, with secure-boot enabled, I cannot boot the Leap 15.4 install iso and I cannot boot Tumbleweed isos. To boot my installed Tumbleweed, I need to use the new shim from Leap 15.4. And to boot my installed Leap 15.3, I need to use the new shim from Leap 15.4. I probably cannot boot the Leap 15.5 Beta iso. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glin@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlee@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c8 --- Comment #8 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Responding to c#4:
Show the current value of SbatLevelRT EFI variable
sbat,1,2022111500 shim 2 grub 3 I'm testing this on a different computer, so I am updating Tumbleweed first (I already updated Leap 15.4). When the update is complete, I'll try the other steps. This change looks like a mistake. In order to tighten secure-boot security they have made changes which force us to disable secure-boot. And that doesn't improve security. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 Frank Kr�ger <fkrueger@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 http://bugzilla.opensuse.org/show_bug.cgi?id=1209985#c9 --- Comment #9 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- A further response to c#4
Show the current value of SbatLevelRT EFI variable
sbat,1,2022111500 shim,2 grub,3
mokutil --set-sbat-policy reset
(I used "delete" rather than "reset") This did not do anything. Rebooting Tumbleweed left SbatLevelRT the same as above. So I tried again, but this time I booted with Leap 15.4 (and its shim). And this time for SbatLevelRT: sbat,1,2021030218 and now I could boot with secure-boot enabled and the Tumbleweed shim. Booting Leap 15.4 again, the SbatLevelRT was: sbat,1,2022052400 grub,2 and I could still boot with the Tumbleweed shim. Another boot of Leap 15.4, and no further changes. I'm guessing that the "set-sbat-policy" change requires MokManager action, and the MokManager with Tumbleweed is too old. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1209985 Thomas Zimmermann <tzimmermann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tzimmermann@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com