Yesterday, I updated my UEFI/BIOS to the latest version (about 11 days old only).
Summary of my HW/OS:
# hostnamectl | grep -v ' ID'
Static hostname: rog-g713pi
Pretty hostname: ASUS ROG Strix G17 G713PI-LL044W
Icon name: computer-laptop
Chassis: laptop 💻
Deployment: production
Operating System: Linux Mint 22.2
Kernel: Linux 6.14.0-33-generic
Architecture: x86-64
Hardware Vendor: ASUSTeK COMPUTER INC.
Hardware Model: ROG Strix G713PI_G713PI
Firmware Version: G713PI.336
Firmware Date: Wed 2025-10-01
Firmware Age: 1w 4d
Immediately after the BIOS update, I downloaded and ran a very popular script to intended to check CVEs mitigation status, if you wish, you can download it from GitHub here.
/root/spectre-meltdown-checker.sh --paranoid
with all-green result, no CVE can be exploited at this point according to the script.
But, since I ran it multiple times, and also with --update-builtin-fwdb
option to update the CPU fw database, re-running it afterward, it says:
* CPU microcode is the latest known available version: NO (latest version is 0xa60120c dated 2024/11/10 according to local firmwares DB v344+i20250812+9d6d)
My laptop CPU in question is AMD Ryzen 9 7845HX, and I do have amd64-microcode
package installed, as well as linux-firmware
package.
The only lines mentioned in dmesg
are these two:
# dmesg | grep microcode
[Sat Oct 11 21:03:36 2025] microcode: Current revision: 0x0a601209
[Sat Oct 11 21:03:36 2025] microcode: Updated early from: 0x0a601209
and
# grep microcode -m 1 /proc/cpuinfo
microcode : 0xa601209
Since I never dealt with this, I want to ask if there possibly is some way to update CPU microcode without waiting for another newer BIOS, which may not come soon?
So, is there some mechanism to update CPU microcode manually? And if so, does it pose any risk?
Thank you.