We’ve identified an issue in version 3.06 that can cause the CPU to get stuck at 545MHz after resuming from sleep. We will release a 3.07 beta around September 8 to address this.
Highlights
- Added Framework’s dbx key and updated the default CA of Windows Secure Boot.
- Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
- Fixed battery drain issues occurring with the Balanced Power Profile.
- Fixed CPU power limits to prevent unnecessary limitation when the GPU is in BOCO mode.
- Introduced Battery Charge Limiting status functionality.
- Introduced the Framework EC device.
Note:
- Once you update to 3.06, you can downgrade to the previous version.
- Install the latest driver bundle 2.05 with BIOS 3.06. Although the Framework EC device will show a yellow bang without it, the system’s functionality remains unaffected.
You can check your current BIOS version following the steps here to determine if you are on the latest release.
After the beta release, we will monitor community feedback, and publish this release to our stable release channel after approximately one week if no major issues are reported.
Subscribing to release notifications
If you want to subscribe to new release notifications you can now opt in through this link to receive an email when we release a new BIOS or driver update for your Framework Laptop.
Battery Extender functionality
With the high energy density on the 85Wh battery, leaving it at 100% state of charge for an extended period of time can shorten the lifetime of the battery. To prevent this, we have added a new feature that automatically limits the maximum state of charge if the system is left plugged into power for more than 5 days. The timer is reset after the system is disconnected from a power adapter for more than 30 minutes.
| Battery Extender Duration | Battery State of Charge |
|---|---|
| 0-5< Days | 99% → 100% |
| 5-7 Days | 90% → 95% |
| >7+ Days | 85% → 87% |
This functionality also reduces cycling of the battery by allowing the battery to discharge by several percent before charging again. Note that in addition to this automatic setting, you can also manually set a lower charge limit on your battery in BIOS to further preserve battery longevity.
This feature can be disabled or enabled in the BIOS Advanced menu.
Battery Extender: This option is enabled by default. If disabled, the system will always keep the battery fully charged.
Battery Extender Trigger: This option sets the number of days that must pass before the battery state of charge is reduced automatically to extend the battery life.
Battery Extender Reset: This option sets the number of minutes that the system is running on battery before the extender is reset, causing the system to charge to 100% when attached to power again.
Battery Charge Limit Functionality
This release modifies the battery charge limit functionality to add a 5% float range. This allows us to reduce the number of microcycles on the battery when the CPU turbos.
Previously to the change in 3.05, the battery would be held at the target state of charge, so if a large power draw happened for a short time, such as when the CPU turbos, the battery would drain slightly and then charge again.
Introduced in this version, the battery will not start to charge until the battery has dropped 5% below the charge limit.
As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on.
If this is activated while the battery state of charge is above the limit, the battery will discharge without drawing power from the adapter until the upper limit is reached.
Downloads
Windows
| Download Link | SHA256 |
|---|---|
| Framework_Laptop_16_Amd_Ryzen7040_BIOS_3.06.exe | 8D8FC08C25A27B848D2C4A40E656A780016F12D8222656589F1688A2272EA46C |
Instructions for Windows Installer:
- Run the .exe.
- Click yes to reboot.
- Wait for the firmware progress bar to complete, and then the system will reboot.
Please note that you must update with a charger attached.
Linux/LVFS
Updating via LVFS is available in the testing channel during the beta period.
You can enable updates from testing by running
fwupdmgr enable-remote lvfs-testing
Please note that you must update with a charger attached, then run:
fwupdmgr refresh --force
then
fwupdmgr get-updates
then
fwupdmgr update
Please note that you must update with a charger attached.
LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.
Linux/Other/UEFI Shell update
| Download Link | SHA256 |
|---|---|
| Framework_Laptop_16_Amd_Ryzen7040_BIOS_3.06.zip | 5E249CE606FEAE29D4E289A49ECE21444A5E79B0187C0401D3529A33F55AF5EA |
Note that if you use the EFI shell update with Windows, you should suspend Bitlocker if enabled before updating using the EFI updater.
Instructions for EFI shell update:
- 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.
Security Fixes
| Module Name | Vulnerability | Score |
|---|---|---|
| CVE-2024-21925 | Improper input validation within the AmdPspP2CmboxV2 driver may allow a privileged attacker to overwrite SMRAM | 8.2 |
| CVE-2024-0179 | SMM Callout vulnerability within the AmdCpmDisplayFeatureSMM driver could allow locally authenticated attackers to overwrite SMRAM | 8.2 |
| CVE-2025-4275 | A vulnerability in the digital signature verification process does not properly validate variable attributes which allows an attacker to bypass signature verification by creating a non-authenticated NVRAM variable. | 7.8 |
| CVE-2025-2884 | TCG TPM2.0 Reference implementation’s CryptHmacSign helper function is vulnerable to Out-of-Bounds read due to the lack of validation the signature scheme with the signature key’s algorithm. | 6.6 |
| CVE-2024-36347 | Improper signature verification in AMD CPU ROM microcode patch loader may allow an attacker with local administrator privilege | 6.4 |
| CVE-2024-49200 | An issue was discovered in AcpiS3SaveDxe and ChipsetSvcDxe in Insyde InsydeH2O with kernel 5.2 though 5.7. A potential DXE memory corruption vulnerability has been identified. | 6.4 |
| CVE-2024-36350 | A transient execution vulnerability in some AMD processors may allow an attacker to infer data from previous stores | 5.6 |
| CVE-2024-36357 | A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache | 5.6 |
| CVE-2024-36348 | A transient execution vulnerability in some AMD processors may allow a user process to infer the control registers speculatively | 3.8 |
| CVE-2024-36349 | A transient execution vulnerability in some AMD processors may allow a user process to infer TSC_AUX | 3.8 |
Enhancements
- Updated to AMD PI 1.2.0.0c.
- Added Framework’s dbx key and updated the default CA of Windows Secure Boot.
- Introduced Battery Charge Limiting status functionality.
- Introduced the Framework EC device.
Fixes
- Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
- Fixed battery drain issues occurring with the Balanced Power Profile.
- Fixed CPU power limits to prevent unnecessary limitation when the GPU is in BOCO mode.
- Fixed “Force Power for Input Modules” setting was not working.
- Security Fixed - CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357, CVE-2024-36347, CVE-2024-0179, CVE-2024-21925, CVE-2024-49200, CVE-2025-2884, CVE-2025-4275.
Important Note
- After updating to this version, you can downgrade to the previous version.
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.
| BIOS | 3.06 | Updated |
|---|---|---|
| EC | ec_306_cf6b79 | Updated |
| PD | 0.0.1E | Same |
| AMD PI | 1.2.0.0c | Updated |
Reporting Issues
To report issues we have created a public issue tracker on github. GitHub · Where software is built We hope that this is a better way to track issues with community involvement moving forward as we have found it difficult to both gather relevant information about issues people are reporting on the forums, and track the issues through their lifecycle in a transparent way.
If you do 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.
If you have an issue regarding hardware, broken devices, returns, etc, this is not the place, please contact support.
Known Issues
- Type-c connection may be unstable with some Apple phones.
- Cannot negotiate charging for certain portable EPR power banks.
- If a device is plugged into an expansion card slot during the update, all USB3/DP functionality will be lost until the device is removed and reinstalled, or the system is fully shut down and powered on again. (Power off, unplug the charger, wait 90 seconds, and then power on again to recover). This issue has an occasional failure rate.
thank you for finally addressing this as it has been a hard pressed topic within this community.
) and then my cpus started acting normal and ramping up to higher frequencies. This was all without another reboot. Anyway, I’ll play around with my various chargers and see what it does. I do not have any 240W to test yet.