Arch Linux

Prosdocimo

Member

Registered: 2024-02-16

Posts: 3

Re: EFI stub: Warning: unable to unprotect memory range

Same here:   "Gigabyte B650M-H (Rev. 1.2)

A few days ago I updated to F40b and this warning started appearing.
Then I went to their BIOS download page and F40b was removed! So I updated to the latest one there, F40, still not fixed.

Them removing the bios was super fishy (oh, and the 'b' suffix doesn't mean beta)

v: F40 date: 05/21/2026
https://www.gigabyte.com/Motherboard/B6 … pport-Bios

I installed the latest BIOS for my motherboard, with basically the same changelog, and no luck: the issue is still there.

I’m starting to wonder whether Windows might be affected by this too, since these are supposed to be standard UEFI protocols. I also have a separate Windows 11 installation on another SSD, but I honestly don’t know how to check it from there (and even if Windows is affected as well, I doubt it would report this kind of issue explicitly during boot). I’ll try to investigate it when I have some time and motivation.

Bedna

Member

Registered: 2025-11-14

Posts: 34

Website

Re: EFI stub: Warning: unable to unprotect memory range

Same here:   "Gigabyte B650M-H (Rev. 1.2)

A few days ago I updated to F40b and this warning started appearing.
Then I went to their BIOS download page and F40b was removed! So I updated to the latest one there, F40, still not fixed.

Them removing the bios was super fishy (oh, and the 'b' suffix doesn't mean beta)

v: F40 date: 05/21/2026
https://www.gigabyte.com/Motherboard/B6 … pport-Bios

Eeeeh, thateeeeh, might have been a bit of me giving them sh*t for not releasing fixes to stable versions, there were 7.1 CVE:s. I also got told the letters does not mean alfa or beta... xD
But F40b was a while ago, after they release a "stable" (that is why I wonder why tf they mean by a,b,c etc is not beta...) they remove the ones with letters, so you must have installed that version (F40b) before feb 2026 when F40 was released. F41b fixed this issue for me.

BUT, this is interesting. This was just two days ago, and my question to them was "when will you release a stable firmware" and they responded with "there are no plans for F41 release", so I installed 41b and the issue is gone, but I found a bunch of other regressions, like not being able to press insert to add to favorites.
And now when I read this, I went to the website AND THERE IS A F41 RELEASE!!

Never ever trust what the support people are saying on their support portal!!! It seems they either don't communicate with the devs, or have no clue what they are talking about...

Edit
I was to quick, I only saw your version, which aligned with my versions, but I have a different mobo.
But if they remove a firmware, it's because exploits were found, I got that explained to me when I got told "a b c" etc is not beta versions.. So that is probably the reason.
They also claim that all versions released by gigabyte is "tested extensively internally"... suuuuuure...
I will NEVER buy gigabyte again.

Last edited by Bedna (2026-06-04 20:31:58)

alba4k

Member

From: Switzerland

Registered: 2021-12-05

Posts: 154

Website

Re: EFI stub: Warning: unable to unprotect memory range

Same on a B650 Aorus Elite AX ICE, upgraded to F41 from F32b and got this issue. Does anyone know what version to downgrade to? it's crazy that this is still an issue after 6 months

Last edited by alba4k (2026-06-07 15:48:11)

Reboot9012

Member

Registered: 2025-11-25

Posts: 21

Re: EFI stub: Warning: unable to unprotect memory range

Maybe this is a windows problem too is there a way to check it somehow ?

Synapse

Member

From: Sweden

Registered: 2025-06-20

Posts: 9

Website

Re: EFI stub: Warning: unable to unprotect memory range

Had this happen to me as well since I updated to 4.03 many months back.
Updating Bios to 4.21 seems to have fixed it for me.
MB: ASRock X870 PRO RS

---

A self-hosting wannabe

alba4k

Member

From: Switzerland

Registered: 2021-12-05

Posts: 154

Website

Re: EFI stub: Warning: unable to unprotect memory range

Updated my B650 Aorus Elite AX ICE from f41 to F42a and the issue is still there

I still get

../systemd/src/boot/linux.c:254@linux_exec: No EFI_MEMORY_ATTRIBUTE_PROTOCOL found, skipping NX_COMPAT support.

Last edited by alba4k (2026-06-18 09:45:24)

UrbenLegend

Member

Registered: 2021-03-26

Posts: 35

Re: EFI stub: Warning: unable to unprotect memory range

Seems like this might have been a deliberate sneaky change by AMD: https://arstechnica.com/security/2026/0 … umer-cpus/

Reboot9012

Member

Registered: 2025-11-25

Posts: 21

Re: EFI stub: Warning: unable to unprotect memory range

Is this the same as https://github.com/AMDESE/AMDSEV/issues/292 and now this
https://www.tomshardware.com/pc-compone … y-feedback

UrbenLegend

Member

Registered: 2021-03-26

Posts: 35

Re: EFI stub: Warning: unable to unprotect memory range

That definitely seems to be referring to the same thing as in my link and I am glad they're reversing course on that change. The thing I am unclear about is whether their disabling of TSME is related to the NX_COMPAT stuff. All I know is that the bad BIOS versions caused both issues.