https://www.tomshardware.com/pc-components/cpus/amds-microcode-vulnerability-also-affects-zen-5-cpus-granite-ridge-turin-ryzen-ai-300-and-fire-range-at-risk Is there a BIOS update to fix this vulnerable in the works? Or was it already patched? Looks like AI 370 is on the list of affected units. SER9.

Hello there, Please send us a picture of the SN on the bottom of the PC. Please press delete key as soon as you turn on the PC, so that you can go to BIOS. Please send us a picture of the Main page. We will check if you need to update the BIOS.

Beelink CS-George I’m running the .73 bios for the SER9 but that’s not the question. https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7033.html Please see the CVE-2024-36347 which affects the AMD CPU. AMD says they released patch to fix the vulnerability March 20, 2025 so we are not protected until we receive a newer BIOS that has the following Platform Initialization (PI) firmware update as noted: StrixHaloPI-FP11 1.0.0.1 (2025-03-20)

rktchip Hi there, please send us a picture of SN on the bottom of the PC and a picture of the Main page of the BIOS. We will transfer it to our R&D for checking.

Did you ever get a resolution for this, rktchip? I can’t tell if the vulnerability has been patched in later SER9 bios, but newer linux kernels have just started checking for it and my (up to date) SER9 is not passing that check “RDSEED32 is broken, disabling the corresponding cpuid bit”

rktchip adrianhand Thank you for raising here this request/concern. There are several AMD CPUs affected and (at least) two different vulnerabilities, so likely multiple Beelink models are also affected. AMD-SB-7033 - AMD CPU Microcode Signature Verification Vulnerability – affects AMD CPUs with Zen 1 up to Zen 5 AMD-SB-7055 - RDSEED Failure on AMD “Zen 5” Processors – affects AMD CPUs with Zen 5 only On both cases they require proper CPU microcode (uCode) updates with the latest patched AGESA™ (AMD Generic Encapsulated System Architecture) versions, readily available from AMD, to be deployed on BIOS/UEFI updates by the OEM mainboard manufacturers. 👉 That means you @Beelink ! Specifically, on my GTR9 Pro model with the AMD Ryzen AI Max+ 395 cpu with the latest BIOS/UEFI version P110 I confirmed that it is still using very old unpatched AGESA version StrixHaloPI-FP11 1.0.0.0c and old microcode (uCode) version 0x0b70001e . These unpatched AGESA and microcode versions and existing RDSEED vulnerability (and mitigation) can also be confirmed on Linux terminal with: $ sudo dmesg | grep microcode [ 0.523280] microcode: Current revision: 0x0b70001e $ sudo dmesg | grep RDSEED32 [ 0.135120] RDSEED32 is broken. Disabling the corresponding CPUID bit. ⚠️ But we know that the latest microcode (uCode) update available from AMD for the AMD Ryzen AI Max+ 395 (family: 0x1a , model: 0x70 , stepping: 0x0 ) cpu is 0x0b700032 . But on the GTR9 Pro we are all on the older unpatched 0x0b70001e . 👉 @Beelink Please provide BIOS/UEFI updates with the latest patched AGESA and microcode (uCode) updates for the several models affected. 🙏

Thank you jotapesse, indeed a firmware update looks like the only way to get it fixed. For the hx370 CPU the latest applicable to Family=0×1a Model=0×24 Stepping=0×00 is patch 0×0b204037. Beelink, please oblige or at least pass comment on alternatives! Now that the CPU instruction set is being partially disabled by newer kernels, the onus really is on beelink to update all firmware embedded microcode to be more recent than the EntrySign vulnerability, which will stop this from being patchable anywhere but the bios.

For anyone who finds this thread via google, at time of writing a bios update for this microcode vulnerability isn’t available and isn’t coming, so bear that in mind if you’re shopping for a mini PC and think that ongoing support, compatibility or security are important. Will update this thread if that ever changes.

Any news Beelink on a bios update with the microcode patch for AMD-SB-7033 included? It’s been 11 months.

Any news @Beelink on a bios update with the microcode patch for AMD-SB-7033 included? The anniversary is coming up.

AMD vulnerability

MrGiantAxe

@adrianhand / @Beelink CS-George is this bios update publicly available yet? latest one I see for the Version 1 is still the P110 bios. https://dr.bee-link.cn/?dir=uploads%2FGTR%2FGTR9-395%2FBIOS

I’d like to have this bios update as well (and with me, many others I guess.)

adrianhand

The one I used is publicly available, yes (https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370-365%2FBIOS%2FSER9-Version5-T408-Note-Solve-RDSEED-Issue-BIOS-version-starts-with-T40X) for the SER9 HX370 specifically. It does appear that other affected machines will need their own separate bios updates.

MrGiantAxe

@adrianhand my bad, thought it was about the GTR9 Pro, but it was another model.

@Beelink CS-George can we get an update on when it will be ready for the GTR9 Pro? May has passed and we are already 8 days into June.

Beelink CS-George

MrGiantAxe The fix for the RDSEED32 issue is currently being finalized and is expected to be released this week. We’ll make the update publicly available on our official download page as soon as it’s ready.
We appreciate your patience and will let everyone know once it goes live.

Beelink CS-George

Beelink CS-George Hi everyone,
The new BIOS firmware that fixes the RDSEED32 issue is now officially released for GTR9 models equipped with the old Intel E610 network card.
If you need this update, please send us via private message:
A photo of your device SN code
A screenshot of the BIOS main interface
After receiving the above materials, we will send you the latest BIOS firmware and detailed flashing instructions right away.

jotapesse

Hi! everyone I just noticed the release of the latest BIOS GTRP112 for the GTR9 Pro v1.0. I updated successfuly my GTR9 Pro v1.0 with it and noticed the following updates for the AGESA™ (AMD Generic Encapsulated System Architecture) and CPU microcode (uCode) versions:

From my previously installed BIOS GTRP110, as documented on my previous comment here, specifically all of the following were updated:

AGESA Version: StrixHaloPI-FP11 1.0.0.0c → 1.0.0.1c

PSP BootLoader Version: 0.40.0.60 → 0.40.0.63
PSP SecureOS Version: 0.40.0.63 → 0.40.0.63

ABL Version: 52.13.10.10  → 53.12.10.12

Ucode Patch Version:  B70001E  → B700034
S3 Image ID: 1A70108000000015  → 1A70108000000016
SMU FW Version: 00.100.112.00  → 10.100.05.00

I also confirmed on my Linux system that those previous related errors and warnings are no longer present and the system is now able to automatically load to the latest available AMD microcode (uCode) update on top of the one included on the BIOS, Current revision: B700037, so it seems to be working great.

$ sudo dmesg | grep microcode
[    1.687645] microcode: Current revision: 0x0b700037
[    1.687646] microcode: Updated early from: 0x0b700034

$ sudo dmesg | grep RDSEED32

Thank you @Beelink @Beelink CS-George and the remaining R&D team! 🙏 This seems to resolve it for the GTR9 Pro v1.0! ✅

Freddit

Is there any ongoing BIOS/UEFI firmware update that resolves the RDSEED32 issue on GTR9 revision 2.x?

Beelink CS-George

Freddit Please repeatedly press delete key as soon as you turn on the PC, go to BIOS. Please send us a picture of the Main page, we will check if you need to update the BIOS.

« Previous Page