this post was submitted on 27 May 2026
49 points (96.2% liked)

Linux

13832 readers
411 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
49
How do I manually check for BIOS security updates from my motherboard manufacturer? (programming.dev)
submitted 4 days ago* (last edited 3 days ago) by Flagstaff@programming.dev to c/linux@programming.dev
16 comments fedilink hide all child comments
 

I read somewhere on Reddit that people who use Linux should periodically, manually check for security updates to their computers' BIOS from their motherboard manufacturers, because Linux apparently ends automatic updates once you leave Windows. I have no idea of where to look on the ASUS website for my Zenbook 14, or if that's even the right place. Could anyone give any guidance on this matter? Is this a thing that we should indeed be doing semiannually or something?

And what else should I be doing on a schedule (even if annually), while I'm at it? Haha.

Edit: thanks, everyone!

you are viewing a single comment's thread
view the rest of the comments
[–] actionjbone@sh.itjust.works 11 points 4 days ago

So, folks who responded are conflating BIOS with UEFI. It's a common mistake - but they are very different things that serve the same purpose.

BIOS is older technology. It usually wasn't risky unless the board was somehow faulty, but there was always some risk because you were directly reflashing the CMOS.

UEFI is the current technology. If your board is less than 10 years old, you almost definitely have UEFI and not BIOS. It's stored in NOR flash memory on the motherboard.

UEFI's nature and design make it much simpler and safer to update. UEFI can be updated automatically within Linux; BIOS requires the board manufacturer's utility to reprogram the CMOS.

I'm simplifying some of this. But this should help explain the conflicting responses of what gets updated under Linux.