{"id":64692,"date":"2024-08-20T20:17:10","date_gmt":"2024-08-21T00:17:10","guid":{"rendered":"http:\/\/pappp.net\/?guid=a881f476d71ce57a41b7daf947fca20c"},"modified":"2024-08-20T20:17:10","modified_gmt":"2024-08-21T00:17:10","slug":"something-has-gone-seriously-wrong-dual-boot-systems-warn-after-microsoft-update","status":"publish","type":"post","link":"https:\/\/pappp.net\/?p=64692","title":{"rendered":"\u201cSomething has gone seriously wrong,\u201d dual-boot systems warn after Microsoft update"},"content":{"rendered":"

Source: Ars Technica<\/a><\/p>\n

Article note: Just like the bad old days, Microsoft updates fucking bootloaders. \nThis seems to be largely justified on the control-granting security theater around secure boot.<\/div>
\n
\n \"“Something\n

Enlarge<\/a> (credit: Getty Images)<\/p> <\/figure>\n\n\n\n\n\n\n

<\/a><\/div>\n

Last Tuesday, loads of Linux users—many running packages released as early as this year—started reporting their devices were failing to boot. Instead, they received a cryptic error message that included the phrase: “Something has gone seriously wrong.”<\/p>\n

The cause: an update<\/a> Microsoft issued as part of its monthly patch release. It was intended to close a 2-year-old vulnerability<\/a> in GRUB<\/a>, an open source boot loader used to start up many Linux devices. The vulnerability, with a severity rating of 8.6 out of 10, made it possible for hackers to bypass secure boot, the industry standard for ensuring that devices running Windows or other operating systems don’t load malicious firmware or software during the bootup process. CVE-2022-2601 was discovered in 2022, but for unclear reasons, Microsoft patched it only last Tuesday.<\/p>\n

Multiple distros, both new and old, affected<\/h2>\n

Tuesday’s update left dual-boot devices—meaning those configured to run both Windows and Linux—no longer able to boot into the latter when Secure Boot was enforced. When users tried to load Linux, they received the message: “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.” Almost immediately support<\/a> and discussion<\/a> forums lit up<\/a> with ​​reports<\/a> of the failure<\/a>.<\/p><\/div>

Read 10 remaining paragraphs<\/a> | Comments<\/a><\/p>","protected":false},"excerpt":{"rendered":"

Enlarge (credit: Getty Images) <\/p>\n

Last Tuesday, loads of Linux users\u2014many running p…<\/p>\n

Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[226],"tags":[],"class_list":["post-64692","post","type-post","status-publish","format-standard","hentry","category-news-2"],"_links":{"self":[{"href":"https:\/\/pappp.net\/index.php?rest_route=\/wp\/v2\/posts\/64692","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pappp.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pappp.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pappp.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pappp.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=64692"}],"version-history":[{"count":0,"href":"https:\/\/pappp.net\/index.php?rest_route=\/wp\/v2\/posts\/64692\/revisions"}],"wp:attachment":[{"href":"https:\/\/pappp.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=64692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pappp.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=64692"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pappp.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=64692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}