Framework Desktop AMD Ryzen™ AI Max 300 Series — BIOS 3.06
Downloads
Section titled “Downloads”- Update AMD PI to 1.0.0.2c.
- Modified the F2 key in the F12 Boot Menu to go to the setup menu instead of the settings menu to allow easier navigation to secure boot settings.
- Added support for the single-ROM BIOS Crisis Recovery feature.
- Implemented a delay in sending the 3A profile to prevent incomplete UCSI PPM command resets during S0 boot transitions.
- Added validation logic to reject invalid USB PD index values.
- Fixed a boot hang issue occurring with specific video encoder cards.
- Resolved an issue where an unidentified UART device appeared in the BIOS, and fixed a bug causing console support to be lost following a BIOS update.
- Fixed an issue where the system was unable to boot from partially locked self-encrypting drives (SEDs)
- Resolved an issue where the iGPU memory size was incorrectly capped at 24 GB on systems populated with 96 GB of system memory.
- Security Fix: CVE-2025-62626 (CVSS Score 7.2) - Improper handling of insufficient entropy in the AMD CPUs could allow a local attacker to influence the values returned by the RDSEED instruction, potentially resulting in the consumption of insufficiently random values.
- Security Fix: CVE-2025-54502 (CVSS Score 7.1) - Incorrect use of boot service in the AMD Platform Configuration Blob (APCB) SMM driver could allow a privileged attacker with local access (Ring 0) to achieve privilege escalation potentially resulting in arbitrary code execution.
- Security Fix: CVE-2024-36345 (CVSS Score 4.6) - Improper input validation in the AMD OverDrive (AOD) System Management Mode (SMM) module could allow a privileged attacker to perform an out-of-bounds read, potentially resulting in loss of confidentiality.
- Security Fix: CVE-2024-36343 (CVSS Score N/A) - libmodbus v3.1.6 was discovered to contain a heap overflow via the modbus_mapping_free() function.
Component Versions
Section titled “ Component Versions ”This BIOS update is a bundle of updates to multiple embedded components in the system. Not all of them use the same version number.
| Component | Version | |
|---|---|---|
| EC | ec_306_bb3566e | Updated |
| PD | 0.0.0E | |
| AMD PI | StrixHaloPI-FP11 1.0.0.2c | Updated |
Installation
Section titled “Installation”BIOS Crisis Recovery Functionality
Section titled “BIOS Crisis Recovery Functionality”At the end of POST, the BIOS hands control off to your operating system. Crisis Recovery is a special alternative mode: instead of booting an OS, the BIOS looks for a firmware update file and re-flashes itself. This lets the system repair its own firmware after a failed or corrupted BIOS flash, for example if a BIOS update was interrupted by a power loss and the machine no longer boots normally.
When To Use BIOS Crisis Recovery
Section titled “When To Use BIOS Crisis Recovery”How Recovery Is Triggered
Section titled “How Recovery Is Triggered”If the BIOS detects that its own code in flash memory has been corrupted, it automatically enters Crisis Recovery and begins searching attached storage for a recovery file. You do not need to press anything.
Prepare the Recovery Drive
Section titled “Prepare the Recovery Drive”On a working system:
- Insert the USB flash drive and format it as FAT32. (This erases the drive)
- On the drive, create the folder path \EFI\FWK (an EFI folder, and inside it an FWK folder).
- Copy the recovery file into that FWK folder.(The CAP file can be got from the EFI updater package) The full path should be: \EFI\FWK\Desktop_AMD_Ryzen_AI_Max_300_RECOVERY.fd (The file name is case-sensitive and must match exactly.)
- Double-check the file name is spelled exactly and with the same capitalization as shown above, ending in .fd.
- Safely eject the drive.
Perform the Recovery
Section titled “Perform the Recovery”On a target system:
- Power off the affected system completely.
- Insert the prepared recovery drive into a USB port on the affected system.
- If the BIOS is corrupted it may enter recovery automatically at power-on.
- The BIOS scans all attached storage (USB and NVMe) for the recovery file in \EFI\FWK, then begins re-flashing. Do not power off or remove the drive during this process. (It may take a few minutes to scan and enter the recovery.)
- Wait for the update to complete and the system to restart. The system should then boot to the operating system normally.
Important!!: Once flashing begins, keep the system powered and do not remove the recovery media until the process finishes. Interrupting a BIOS flash can leave the system unbootable.
You can check your current BIOS version following the steps here to determine if you are on the latest release.
Framework firmware is published to LVFS and updates via fwupd, which ships by default on most modern
distributions.
fwupdmgr refresh --forcefwupdmgr get-updatesfwupdmgr updateWindows
Section titled “Windows”- Download the Framework Desktop AMD Ryzen™ AI Max 300 Series BIOS 3.06 Windows Installer.
- Run the
.exeand click "Yes" when prompted to reboot. - Wait for the firmware progress bar to complete — the system will reboot automatically. Do not interrupt.
EFI Shell Update
Section titled “ EFI Shell Update ”- Download the EFI Shell Update v3.06.
- Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.
- Attach a charger to your device while updating.
- Boot your system while pressing F12 and boot from the thumb drive.
- Let startup.nsh run automatically.
- Follow the instructions to install the update.
Known Issues
Section titled “ Known Issues ”- Certain USB-C peripherals may exhibit intermittent compatibility issues during the PD or DisplayPort Alt Mode handshake.
Reporting Issues
Section titled “Reporting Issues”Please use the public issue tracker on GitHub to report issues.
If you experience an issue with the update that is related to your system firmware, please post as complete a description as you can, including relevant system information and external peripherals. Please note that we do not currently have a SLA for responding to issues on github, but we will be reviewing them through the bios release process, and will review them for future updates as well.
Please contact support if you have an issue regarding hardware, broken devices, returns, etc.