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-2026-6726 (CVSS Score 7.9) - An information leakage vulnerability was reported in the TCG TPM 2.0 reference code that could allow a local attacker with elevated privileges to obtain a credential from a TPM-aware CA for a falsified TPM key (such as an Attestation Key, DevID Key or TLS authentication key) and falsify other TPM 2.0 attestations with this key. See also TCG VRT0010.
- 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-2026-6727 (CVSS Score 5.9) - A timing side-channel vulnerability exists in the RSA OAEP decryption implementation. A privileged local attacker with access to the TPM command interface may be able to exploit timing differences to recover information that could allow decryption of ciphertexts encrypted to TPM-managed RSA keys, including the RSA Endorsement Key (EK), including import blobs, credential blobs, and session salts. Under certain conditions, this may also enable the forgery of TPM 2.0 attestations. Refer to TCGVRT0011.
- 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 |
Windows Driver Component Versions
Section titled “ Windows Driver Component Versions ”| Driver | Version | |
|---|---|---|
| AMD Chipset Driver | 8.05.04.516 | Updated |
| AMD Graphics Driver | 26.6.4 (v32.0.31021.5001) | Updated |
| Realtek Audio Driver | 6.0.9859.1 | |
| Realtek Audio Console | 1.53.374.0 | |
| RZ717 WiFi Driver | 5.6.0.4444 | |
| RZ717 Bluetooth Driver | 1.1043.0.555 | |
| Realtek Lan | 1126.20.729.2024 | |
| AMD DRTM | 1.0.18.4 | |
| AMD MEP Driver | 32.2.0.4 | Updated |
| Microsoft MEP Driver | 2.0.28 | Updated |
| Framework EC Driver | 0.0.0.6 | |
| Realtek Ethernet (Expansion Card) | 11013_20_07272023_08042023 | |
| SD Card Reader | v4_5_10_201 | |
| 2nd Gen uSD Card Reader | v4_5_10_202 |
Installation
Section titled “Installation”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.
- Download and install the Windows Driver Bundle v1.04 for your system if you are currently using a previous Driver Bundle release, or you are installing the Driver Bundle for the first time.
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.
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.
Crisis Recovery allows the system to 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.
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). - Download the EFI Shell Update (BIOS v3.06) and locate the CAP file.
Rename the recovery file to
Framework_Desktop_AMD_Ryzen_AI_Max_300_RECOVERY.fdand copy it into the\EFI\FWKfolder.- Safely eject the drive.
Perform the Crisis Recovery
Section titled “Perform the Crisis Recovery”On a target system:
- Power off the affected system completely.
- Insert the prepared recovery drive into a USB port on the affected system.
- Power on the system. If the BIOS is corrupted it will enter recovery automatically at power-on.
- Wait for the update to complete and the system to restart. The system should then boot to the operating system normally.
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.