Framework Laptop 12 13th Gen Intel® Core™ — BIOS 3.09

Downloads

FileRelease Date

Windows BIOS v3.09 Installer2026-09-08Framework_Laptop_12_13th_Gen_Intel_Core_BIOS_3.09_2Stages_Updater.zipSHA256 · F4FE64056031FEA3514FBA9D2D6AEDC82DD2451A6683CDB32B6330FEB1AED41D

Windows Driver Bundle v1.032026-09-08Framework_Laptop_12_13th_Gen_Intel_Core_driver_bundle_W11_v103_2026_08_18.exeSHA256 · F88F5F1A64DBD6531A34CD667868D41B2BE160361415F4A7E9E0B10F4DE0B640

Wi-Fi Driver for use during Windows Installation2026-09-03Framework_W11_OOBE_Wifi_Driver_Package.zipSHA256 · BD427CC233BAAA7CC8522823603390A50FA425BC302D2192CB7900017B5BD044

EFI Shell Update (BIOS v3.09)2026-09-08Framework_Laptop_12_13th_Gen_Intel_Core_BIOS_3.09_2Stages_Updater_EFI.zipSHA256 · F5F89CCE6CCD47E21A8EA6726DF59C96EC091676AD2B3982C512FB09880505AD

BIOS

3.09

Released 2026-09-08·20 MB

Stable

Latest

Highlights

• Updated Microcode to 0x6134.
• Updated CSME firmware to 16.1.40.2765v3.
• Added support for Gen 2 HID Keyboards.
• Added support for the single-ROM BIOS Crisis Recovery feature.
• Added fingerprint reader support and power control integration.
• Fixed an issue where Battery Extender status reported incorrectly following a reboot, hibernation, or shutdown after timer expiration.
• Fixed an issue where PROCHOT# might fail to release upon entering system sleep.
• Remapped key event on input deck: F12 now sends KEY_CONFIG instead of KEY_MEDIA.
• Updated thermal tables to improve system stability.
• Security fix: CVE-2025-31648 — Improper handling of values in the microcode flow for some Intel(R) Processor Family may allow an escalation of privilege. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (low), integrity (low) and availability (none) impacts. (CVSS N/A)
• Security fix: CVE-2025-27708 — Out-of-bounds read in the firmware for some Intel(R) Converged Security and Management Engine (CSME) Firmware (FW) within Ring 0: Kernel may allow an information disclosure. System software adversary with a privileged user combined with a low complexity attack may enable data exposure. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts. (CVSS N/A)
• Security fix: CVE-2025-20080 — Null pointer dereference in the firmware for some Intel(R) AMT and Intel(R) Standard Manageability within Ring 0: Kernel may allow a denial of service. Network adversary with an unauthenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts. (CVSS N/A)
• Security fix: CVE-2025-32008 — Out-of-bounds write in the firmware for the Intel(R) AMT and Intel(R) Standard Manageability within Ring 3: User Applications may allow a denial of service. Network adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (low) impacts. (CVSS N/A)

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
Intel SIC	0C.01.F6.20
Intel CSME	16.1.40.2765v3	Updated
MCU	0x6134	Updated
GOP	21.0.1066
EC	ec_309_9a48264	Updated
PD	0.0.12

Windows Driver Component Versions

Driver	Version
FrameworkLaptop12Ppkg	1.0
Intel Chipset	10.1.20389.8776
Intel GNA	03.05.00.1578
Intel Management Engine	2601.9.16.0
Intel Serial IO	30.100.2417.30
Intel Graphics	32.0.101.7085
Intel Graphics Command Center	1.100.5688.0
Intel Dynamic Tuning	9.0.11701.44281
Intel Smart Sound	10.29.00.10981
Realtek Audio	6.0.9969.1
Realtek Audio Console	1.53.393.0
Intel PROSet WiFi	24.30.1.1
Intel PROSet Bluetooth	24.30.1.1
ILITEK Wake On Touch Device	10.0.19041.868
Fingerprint Driver	3.91.6901.7399	Updated
Framework EC	0.0.0.6
Framework Sensor	0.0.7.0
Realtek Ethernet (Expansion Card)	11013_20_07272023_08042023
SD Card Reader (Expansion Card)	v4_5_10_201
2nd Gen uSD Card Reader (Expansion Card)	v4_5_10_202

Installation

Note

1. Upgrading to version 3.09 requires a minimum baseline of BIOS version 3.08. Updating directly from an older version will prevent the system from powering on.

2. Rollbacks from version 3.09 are permanently blocked due to an increase in the EC image size.

3. This is a two-stage BIOS update process.

   • Windows: Please run the 3.08 updater first, and then execute the 3.09 updater once that completes.

   • Linux: If your system is running a BIOS version lower than 3.08, LVFS will only offer version 3.08 initially. Once you complete the update to 3.08, version 3.09 will become visible in LVFS, allowing you to proceed with the final update.

   • EFI: The EFI updater will automatically detect your current BIOS version and execute the appropriate installer—running version 3.08 or 3.09 based on your system’s baseline.

You can check your current BIOS version following the steps here to determine if you are on the latest release.

Note

You must update with a charger attached.

Linux

Framework firmware is published to LVFS and updates via fwupd, which ships by default on most modern distributions.

fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update

Caution

LVFS may not update if the battery is at 100%.
If you experience issues, discharge to 95%, plug AC back in, then re-run fwupdmgr update.

Windows

1. Download the Framework Laptop 12 13th Gen Intel® Core™ BIOS 3.09 Windows Installer.

2. Ensure your system is plugged into power and your battery is charged.

3. Extract the contents of the zip.

4. Run the following updates in sequence. After each file is run your system will automatically restart.

   1. Framework_Laptop_12_13th_Gen_Intel_Core_BIOS_3.08_Step1.exe
   2. Framework_Laptop_12_13th_Gen_Intel_Core_BIOS_3.09_Step2.exe

5. Wait for the firmware progress bar to complete — the system will reboot automatically. Do not interrupt.

6. Download and install the Windows Driver Bundle v1.03 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

Note

If you use the EFI shell update with Windows, you should suspend Bitlocker if enabled before updating using the EFI updater.

1. Download the EFI Shell Update v3.09.

2. 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.

3. Attach a charger to your device while updating.

4. Boot your system while pressing F12 and boot from the thumb drive.

5. Let startup.nsh run automatically to update to 3.08. The system will reboot several times and apply CSME update.

6. Once updated to 3.08, boot your system while pressing F12 and boot from the thumb drive again.

7. Let startup.nsh run automatically to update to 3.09.

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.

Note

Use these steps if your system fails to power on to the OS after a BIOS update, shows no display, or you were instructed to perform a BIOS recovery.

If your system still boots normally, you do not need this procedure.

Prepare the Recovery Drive

On a working system:

1. Insert the USB flash drive and format it as FAT32. (This erases the drive)
2. On the drive, create the folder path \EFI\FWK (an EFI folder, and inside it an FWK folder).
3. Download the EFI Shell Update (BIOS v3.09) and locate the CAP file.

4. Rename the recovery file to Framework_Laptop_12_13th_Gen_Intel_Core_RECOVERY.fd and copy it into the \EFI\FWK folder.

   Caution

   The file path is case-sensitive and must match exactly.

   • DirectoryEFI

     • DirectoryFWK

       • Framework_Laptop_12_13th_Gen_Intel_Core_RECOVERY.fd

   Double-check the filename is named with the same capitalization shown above and the filename ends in .fd.

5. Safely eject the drive.

Perform the Crisis Recovery

On a target system:

1. Power off the affected system completely.
2. Insert the prepared recovery drive into a USB port on the affected system.
3. Power on the system. If the BIOS is corrupted it will enter recovery automatically at power-on.

   Note

   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 recovery media during this process. (It may take a few minutes to scan and enter the recovery.) Interrupting a BIOS flash can leave the system unbootable.
4. Wait for the update to complete and the system to restart. The system should then boot to the operating system normally.

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.

Other Releases

13th Gen Intel® Core™ — BIOS & DriversView all BIOS and driver releases for the Framework Laptop 12 13th Gen Intel® Core™.