UEFI

UEFI. The Unified Extensible Firmware Interface is a modern specification that defines a software interface between an operating system and platform firmware. It is designed to replace the older legacy BIOS system found in IBM PC compatible computers, offering improved security, faster boot times, and support for larger hard disk drives. The standard is developed and maintained by the UEFI Forum, a consortium of industry-leading technology companies.

● Overview

UEFI serves as a critical intermediary layer, initializing computer hardware components during the booting process before handing control to the OS loader. It provides a standardized environment for pre-boot applications, offering capabilities far beyond the simple text mode interface of its predecessor. This firmware standard is essential for modern systems, enabling advanced features like Secure Boot and support for GUID Partition Table disks larger than 2 terabytes. Its modular design allows original equipment manufacturers to add custom drivers and applications, creating a rich pre-OS environment.

● History and development

The initial framework, then called the Extensible Firmware Interface, was created by Intel Corporation for its Itanium-based servers in the late 1990s, aiming to address BIOS limitations. In 2005, Intel handed over stewardship to the newly formed UEFI Forum, which included major partners like Microsoft, AMD, Apple Inc., and various IBM hardware vendors. The release of Microsoft Windows 8 in 2012, with its requirement for UEFI-based Secure Boot, was a pivotal moment for widespread adoption in the consumer market. Subsequent versions of Windows 10 and Windows 11 have further cemented its role, while it is also fully supported by modern Linux kernel distributions and macOS on Apple silicon.

● Technical specifications

The specification defines a set of protocols and Application Programming Interface services for the pre-boot environment. It executes from non-volatile storage, such as SPI flash memory, and can leverage the CPU's protected mode from the outset, unlike the real mode operation of legacy BIOS. Key components include the GUID Partition Table for disk partitioning, the UEFI system partition for storing bootloaders, and a comprehensive driver model supporting graphics output protocol for high-resolution interfaces. The firmware itself is often written in C (programming language), and its modular extensions can be loaded from various non-volatile memory sources.

● Comparison with legacy BIOS

Unlike the legacy BIOS, which relies on Master Boot Record partitioning and 16-bit assembly language code, UEFI operates in 32-bit or 64-bit mode, enabling direct access to all system memory and modern peripherals. The traditional BIOS was constrained by the IBM PC AT hardware design and the 640 KB conventional memory barrier, whereas UEFI has no such architectural limits. While BIOS interaction occurs through software interrupt calls like INT 13h, UEFI uses a suite of protocol-based services, making the boot process more reliable and faster, especially on systems with many solid-state drives.

● Security features

A cornerstone of UEFI security is the Secure Boot protocol, which uses cryptographic signatures to verify that each piece of boot software, from the OS loader to UEFI drivers, is trusted before execution, helping to block rootkits and bootkits. The specification also defines UEFI Secure Boot Key Exchange mechanisms for managing public key infrastructure databases. Complementary features like Measured Boot, which logs the boot sequence to a Trusted Platform Module, and Intel Boot Guard help ensure firmware integrity from the CPU's first instruction.

● Implementation and adoption

Virtually all new x86-64 and ARM architecture-based personal computers and servers ship with UEFI firmware, often provided by companies like Insyde Software, American Megatrends, and Phoenix Technologies. Major operating systems, including Microsoft Windows, Linux distributions like Ubuntu and Fedora (operating system), and macOS, have native support. The EDK II (EFI Development Kit II) is the open-source reference implementation used by many firmware developers. Adoption was accelerated by requirements in the Windows Hardware Certification Program.

● Criticism and limitations

Critics have argued that features like Secure Boot could potentially hinder open-source software installation or create lock-in for specific operating system vendors, though most implementations now include options to manage custom keys. The increased complexity of the UEFI codebase, sometimes compared to a miniature operating system, expands the attack surface for sophisticated firmware vulnerabilities, as demonstrated by research into threats like LoJax. Some implementations have also been criticized for providing poor user interface experiences or inconsistent Advanced Configuration and Power Interface settings menus across different OEM vendors.

Category:BIOS Category:Computer standards Category:Firmware