View source for Unified Extensible Firmware Interface

{{jargon|date=February 2024}}
{{update|date=February 2024}}
{{Use dmy dates|date=February 2020}}

[[File:Efi-simple.svg|thumb|EFI in the boot sequence]]
The '''Unified Extensible Firmware Interface''' ('''UEFI''')<ref>Pronounced as an acronym or as {{IPAc-en|'|uː|ᵻ|f|aɪ}}.</ref> is in the [[Boot device|boot sequence]] before the [[operating system]] and after the [[firmware]]. UEFI replaces the legacy [[BIOS]] firmware interface found in all [[IBM]] [[Personal computer|computers]].<ref name="Intel2000">{{cite web|url=http://systems.cs.colorado.edu/Documentation/IntelDataSheets/xscalemagazine.pdf|title=Solving BIOS Boot Issues with EFI|first=Michael|last=Kinney|date=1 September 2000|access-date=14 September 2010|pages=47–50|archive-date=23 January 2007|archive-url=https://web.archive.org/web/20070123141151/http://systems.cs.colorado.edu/Documentation/IntelDataSheets/xscalemagazine.pdf|url-status=dead}}</ref><ref name="ElReg1" /> Most UEFI implementations are backwards-compatible to the legacy BIOS. UEFI supports remote [[Diagnosis|diagnostics]] and [[Repair|repairing]] of computers, even when there isn't an operating system.<ref>{{cite web|url=http://h30565.www3.hp.com/t5/Feature-Articles/The-30-year-long-Reign-of-BIOS-is-Over-Why-UEFI-Will-Rock-Your/ba-p/198|archive-url=https://web.archive.org/web/20130626000135/http://h30565.www3.hp.com/t5/Feature-Articles/The-30-year-long-Reign-of-BIOS-is-Over-Why-UEFI-Will-Rock-Your/ba-p/198|archive-date=26 June 2013|title=The 30-year-long Reign of BIOS is Over: Why UEFI W... - Input Output|website=HP.com|access-date=6 March 2012}}</ref>

[[Intel]] made the '''Extensible Firmware Interface''' ('''EFI'''). Some of the EFI's usage and formats mimic those of [[Microsoft Windows|Windows]].<ref>[https://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html IBM PC Real Time Clock should run in UT]. Cl.cam.ac.uk. Retrieved on 30 October 2013.</ref><ref name="Matthew Garrett">{{cite web|url=https://www.youtube.com/watch?v=V2aq5M3Q76U#t=14m45s|archive-url=https://ghostarchive.org/varchive/youtube/20211113/V2aq5M3Q76U|archive-date=2021-11-13|url-status=live|title=EFI and Linux: The Future Is Here, and It's Awful|first=Matthew|last=Garrett|date=19 January 2012|work=[[linux.conf.au]] 2012|access-date=2 April 2012}}{{cbignore}}</ref> In 2005, EFI 1.10 (the final release) was [[deprecated]].

== History ==

===Creation===
The [[motivation]] for EFI came during early development of the first Intel–HP [[Itanium]] systems in the mid-1990s. Limitations had become too restrictive for the [[server]] platforms Itanium was looking for.<ref name="EmulexUEFI" /> The effort to address these restrictions began in 1998 and was first called the ''Intel Boot Initiative''.<ref>{{citation|url=http://www.intel.com/technology/efi/|archive-url=https://web.archive.org/web/20100105051711/http://www.intel.com/technology/efi/|archive-date=5 January 2010|title=Extensible Firmware Interface (EFI) and Unified EFI (UEFI)|publisher=Intel}}</ref> It was renamed to ''Extensible Firmware Interface'' (EFI).<ref>{{citation|first=Dong|last=Wei|title=Beyond BIOS|chapter=foreword|publisher=Intel Press|year=2006|isbn=978-0-9743649-0-2}}</ref><ref>{{citation|chapter-url=http://www.intel.com/technology/efi/main_specification.htm|title=Extensible Firmware Interface|chapter=1.10 Specification overview|publisher=Intel}}</ref>

In July 2005, Intel stopped its development of the EFI specification at version 1.10, and gave it to the [[Unified EFI Forum]], which has developed the specification as the ''Unified Extensible Firmware Interface'' (UEFI). The original EFI specification remains owned by Intel, which exclusively provides licenses for EFI-based products, but the UEFI specification is owned by the UEFI Forum.<ref name="EmulexUEFI">{{cite news|title=Emulex UEFI Implementation Delivers Industry-leading Features for IBM Systems|publisher=Emulex|url=http://www.emulex.com/artifacts/757d23e7-8acb-41a7-872a-afb733ab0688/elx_tb_all_uefi_ibm.pdf|access-date=14 September 2010}}</ref><ref>{{citation|url=http://www.uefi.org/about/|publisher=Unified EFI Forum|title=About|quote=Q: What is the relationship between EFI and UEFI? A: The UEFI specification is based on the EFI 1.10 specification published by Intel with corrections and changes managed by the Unified EFI Forum. Intel still holds the copyright on the EFI 1.10 specification, but has contributed it to the Forum so that the Forum can evolve it. There will be no future versions of the EFI specification, but customers who license it can still use it under the terms of their license from Intel. The license to the Unified EFI Specification comes from the Forum, not from Intel}}</ref>
===Versions===
Version 2.0 of UEFI was released on 31 January 2006. It added [[cryptography]] and [[security]].

Version 2.1 of UEFI was released on 7 January 2007. It added [[network]] [[authentication]] and the [[user interface]] [[architecture]].

The latest UEFI specification, version 2.9, was released in March 2021.<ref name="UEFISpec2.9">{{cite web|url=https://uefi.org/sites/default/files/resources/UEFI_Spec_2_9_2021_03_18.pdf|title=Unified Extensible Firmware Interface (UEFI) Specification Version 2.9|website=[[UEFI|www.uefi.org]]|date=March 2021|access-date=23 May 2021}}</ref>
===Open source===
The first [[open source]] UEFI implementation, Tiano, was released by Intel in 2004. Tiano has since then been succeeded by EDK<ref>{{Cite web|url=https://github.com/tianocore/edk|title=GitHub - tianocore/Edk: Git mirror of EDK.|website=[[GitHub]]|date=19 March 2019}}</ref> and EDK2<ref>{{Cite web|url=https://github.com/tianocore/tianocore.github.io/wiki/EDK-II|title=GitHub - tianocore/Tianocore.github.io: Tianocore website.|website=[[GitHub]]|date=8 August 2019}}</ref> and is now maintained by the [[TianoCore]] community.<ref>{{Cite web|url=https://www.tianocore.org/|title=What is TianoCore?}}</ref>

== Advantages ==
UEFI firmware provides several technical advantages over a traditional BIOS system:<ref name="UEFI2009Microsoft">{{cite web|url=http://www.microsoft.com/whdc/system/platform/firmware/UEFI_Windows.mspx|title=UEFI and Windows|publisher=Microsoft|date=15 September 2009|access-date=14 September 2010}}</ref>

* Being able to boot a disk containing large partitions (over 2 [[Terabyte|TB]]) with a [[GUID Partition Table]] (GPT)<ref name="grub-bios-installation">{{cite web|url=https://www.gnu.org/software/grub/manual/html_node/BIOS-installation.html|title=Installation|work=3.4 BIOS installation|access-date=25 September 2013|publisher=[[GNU GRUB]]}}</ref>{{Efn|name="note1"|Large disk support and features such as [[Advanced Configuration and Power Interface]] (ACPI) and [[SMBIOS|System Management BIOS]] (SMBIOS) were subsequently implemented in BIOS-based systems.}}<ref name="Non-boot GPT disk">{{cite web|url=https://superuser.com/a/1245320/1291014|title=Non-boot disks can use a GPT partition table even with no UEFI bios}}</ref>
* Flexible pre-OS environment, including network capabilities, a [[Graphical user interfaces and consoles|GUI]], and multi language support
* 32-bit (for example [[IA-32]]) or 64-bit (for example [[x64]]) pre-OS environment
* [[C (programming language)|C language]] programming
* [[Modular]] design
* Backward and forward compatibility with the Legacy BIOS

== Features ==

=== {{Anchor|GOP|MM|VARIABLE|TIME}}Services ===

==== Graphics Output Protocol (GOP) services ====
: The ''Graphics Output Protocol'' (GOP) gives runtime services; see also [[Unified Extensible Firmware Interface#Graphics features|Graphics features]] below. The operating system is allowed to write to the [[framebuffer]] provided by GOP during runtime mode.<ref>{{Cite web|title=What is efifb? — The Linux Kernel documentation|url=https://www.kernel.org/doc/html/latest/fb/efifb.html|access-date=2020-11-24|website=www.kernel.org}}</ref>

==== Variable services ====
: UEFI variables provide a way to store data, in particular non-volatile data. Some UEFI variables are shared between platform [[firmware]] and operating systems. Variable namespaces are identified by [[GUID]]<nowiki/>s, and variables are key/value pairs.  UEFI variables can be used to keep [[crash messages]] in [[Non-volatile random-access memory|NVRAM]] after a crash for the operating system to get after a reboot.<ref name="theh-brickwindows">{{cite web|title=Samsung UEFI bug: Notebook bricked from Windows|url=http://www.h-online.com/open/news/item/Samsung-UEFI-bug-Notebook-bricked-from-Windows-1801439.html|access-date=27 February 2013|publisher=The H}}</ref>

==== Time services ====
: UEFI provides time services. Time services include support for someone's [[time zone]] and [[Daylight saving time|daylight saving]] fields, which allow the hardware's [[real-time clock]] to be set to local time or [[UTC]].<ref>UEFI specification, section 7.3</ref> On machines using a PC-AT real-time clock, by default the hardware clock still has to be set to local time for compatibility with BIOS-based Windows,<ref name="Matthew Garrett" /> unless using recent versions and an entry in the [[Windows registry]] is set to indicate the use of UTC.

=== {{Anchor|APPLICATIONS}}Applications ===
[[File:Efi_flowchart_extended.svg|thumb|Interaction between the EFI boot manager and EFI drivers]]

Beyond loading an OS, UEFI can run ''UEFI applications'', which stay as files on the [[EFI System Partition]]. They can be executed from the UEFI Shell, by the firmware's [[Unified Extensible Firmware Interface#BOOT-MANAGER|boot manager]], or by other UEFI apps. ''UEFI apps'' can be developed and installed independently of the [[original equipment manufacturers]] (OEMs).

A type of UEFI application is an OS [[boot loader]] such as [[GRUB]], [[rEFInd]], [[Gummiboot (software)|Gummiboot]], and [[Windows Boot Manager]]; which loads some OS files into memory and executes them. Also, an OS boot loader can provide a user interface to allow the selection of another UEFI application to run. Utilities like the UEFI Shell are also UEFI applications.

=== Protocols ===
EFI defines [[Communication protocol|protocols]] as a set of software interfaces used for communication between two [[binary modules]]. All EFI drivers must provide services to others via protocols. The EFI Protocols are similar to the [[BIOS interrupt calls]].

=== Graphics features ===
The EFI 1.0 specification defined a [[Universal Graphic Adapter)]] [[Communication protocol|protocol]] as a way to support graphics features. UEFI did not include it and replaced it with [[Graphics Output Protocol|GOP (Graphics Output Protocol)]].<ref>{{cite web|url=http://www.intel.com/content/www/us/en/intelligent-systems/intel-embedded-graphics-drivers/faq-bios-firmware.html|title=Intel Embedded Graphics Drivers FAQ: BIOS and firmware|access-date=19 May 2014|publisher=[[Intel]]}}</ref>

UEFI 2.1 defined a "Human Interface Infrastructure" to manage user input, localized strings, fonts, and forms (in the [[HTML]] sense). These enable [[Original equipment manufacturer|original equipment manufacturers]] (OEMs) or [[Independent BIOS vendor|independent BIOS vendors]] (IBVs) to design graphical interfaces for pre-boot configuration.

Most early UEFI [[firmware]] implementations were [[console]]-based. Today many UEFI firmware implementations are [[Graphical user interfaces and consoles|GUI]]-based.

=== Boot stages ===
SEC – Security Phase is the first stage of the UEFI boot but may have platform specific code. It is built as code written in [[assembly language]] for the specific architecture. It initializes temporary memory (often CPU [[Cache (computing)|cache]] as RAM) and serves as the system's software root of trust.

PEI – Pre-EFI Initialization. This second stage of UEFI contains a dependency-aware [[dispatcher]] that loads and runs PEI modules to handle hardware tasks such as [[main memory]] initialization and firmware recovery operations. It's also responsible for the discovery of the boot mode and handling many [[ACPI]] S0ix/[[ACPI]] S3 operations. In the case of ACPI S0ix/ACPI S3 resume, it is responsible for restoring many hardware registers to a pre-sleep state. PEI also uses CPU cache as RAM.

DXE – Driver Execution Environment is made of C modules and a dependency-aware [[dispatcher]]. With main memory now available, CPU, chipset, mainboard and boot devices are initialized in DXE and BDS.

BDS – Boot Device Select  is a part of the DXE.<ref>{{Cite web|url=https://github.com/tianocore/tianocore.github.io/wiki/PI-Boot-Flow|title=PI Boot Flow · tianocore/Tianocore.github.io Wiki|website=[[GitHub]]}}</ref><ref>{{Cite web|url=https://ami.com/en/?Aptio_V_Status_Codes.pdf|title=Engineering Services}}</ref> In this stage, boot devices are initialized, UEFI drivers or [[Option ROM|Option ROMs]] of PCI devices are executed according to system configuration, and boot options are [[processed]].

TSL – Transient System Load  is the stage between boot device selection and hand-off to the OS. At this point one may enter UEFI shell, or execute an UEFI application such as the OS boot loader.

RT – Runtime - The UEFI hands off to the [[operating system]] (OS) after {{Mono|ExitBootServices()}} is executed. A UEFI compatible OS is now responsible for exiting boot services triggering the firmware to unload all no longer needed code and data, leaving only runtime services code/data, e.g. [[System Management Mode|SMM]] and [[Advanced Configuration and Power Interface|ACPI]].<ref>{{Cite web|title=The Unified Extensible Firmware Interface (UEFI) — The Linux Kernel documentation|url=https://www.kernel.org/doc/html/latest/arm/uefi.html|access-date=2020-11-07|website=www.kernel.org|archive-date=2020-10-25|archive-url=https://web.archive.org/web/20201025170840/https://www.kernel.org/doc/html/latest/arm/uefi.html|url-status=dead}}</ref> A typical modern OS will prefer to use its own programs (such as [[Kernel driver|kernel drivers]]) to control hardware devices.

When a legacy OS is used, CSM will handle this call making sure that the system is compatible with legacy BIOS expectations.

== Criticism ==
Many digital rights activists have protested against UEFI. Some experts have blamed UEFI as an attempt to remove the ability of the user to control the computer.<ref name="FosdemInterviewRonaldGMinnich">{{cite web|url=https://archive.fosdem.org/2007/interview/ronald%2bg%2bminnich.html|title=Interview: Ronald G Minnich|publisher=Fosdem|date=6 February 2007|access-date=14 September 2010}}</ref><ref>{{citation|url=http://boingboing.net/2011/12/27/the-coming-war-on-general-purp.html|title=The Coming War on General Purpose Computation|first=Cory|last=Doctorow|date=27 December 2011|access-date=25 September 2013}}</ref> It does not solve the BIOS's long-standing problems of requiring two different drivers—one for the firmware and one for the operating system—for most hardware.<ref name="YouTubeCorebootFirmware">{{cite web|url=https://www.youtube.com/watch?v=X72LgcMpM9k|title=coreboot (aka LinuxBIOS): The Free/Open-Source x86 Firmware|publisher=YouTube|date=31 October 2008|access-date=14 September 2010}}</ref>

Open-source project [[TianoCore]] also provides UEFI interfaces.<ref>{{citation|chapter-url=http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Welcome|publisher=SourceForge|title=TianoCore|chapter=Welcome|url-status=dead|archive-url=https://web.archive.org/web/20120423101551/http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Welcome|archive-date=23 April 2012|df=dmy-all}}</ref> TianoCore doesn't have the specialized drivers that initialize functions, which are instead provided by [[coreboot]], of which TianoCore is one of many payload options. The development of coreboot requires cooperation from [[Central processing unit|CPU]] manufacturers to provide the specifications needed to develop initialization drivers.

=== {{Anchor|Secure Boot criticism}}Secure Boot ===
{{See also|Windows 8#Reception}}
[[File:Secure_Boot_keys_example_screenshot.png|thumb|Examples of custom Secure Boot public keys]]
[[File:Shim_MokManager_screenshot.png|thumb|MokManager, a part of Shim bootloader]]
In 2011, [[Microsoft]] announced that computers certified to run its [[Windows 8]] operating system had to release with Microsoft's public key enrolled and Secure Boot enabled.{{Citation needed|date=February 2022}} Following the announcement, Microsoft was accused by critics and [[Free and open-source software|free software/open source]] advocates (including the [[Free Software Foundation]]) of trying to use the Secure Boot functionality of UEFI to prevent the installation of alternative operating systems such as [[Linux]]. Microsoft denied that the Secure Boot requirement was intended to serve as a form of [[Vendor lock-in|lock-in]]. They also clarified its requirements by stating that 32-bit-based systems certified for Windows 8 must allow Secure Boot to enter custom mode or be disabled, but not on systems using the [[ARM architecture]].<ref name="pcw-ueficontroversy">{{cite web|title=Windows 8 Secure Boot: The Controversy Continues|url=https://www.pcworld.com/article/248342/windows_8_secure_boot_the_controversy_continues.html|website=PC World|access-date=9 September 2012}}</ref><ref name="cwuk-arm">{{cite web|url=http://www.computerworlduk.com/blogs/open-enterprise/is-microsoft-blocking-linux-booting-on-arm-hardware-3569162/|title=Is Microsoft Blocking Linux Booting on ARM Hardware?|publisher=Computerworld UK|access-date=6 March 2012}}</ref> [[Windows 10]] allows [[Original equipment manufacturer|OEMs]] to decide whether or not Secure Boot can be changed by users of their 32-bit systems.<ref name="arstechnica-securebootw10">{{cite web|title=Windows 10 to make the Secure Boot alt-OS lock out a reality|url=https://arstechnica.com/information-technology/2015/03/windows-10-to-make-the-secure-boot-alt-os-lock-out-a-reality/|website=Ars Technica|date=20 March 2015 |access-date=21 March 2015}}</ref>
====Concerns====
Other developers concerned about the issues of implementing support for Secure Boot on [[Linux]] systems in general. Former [[Red Hat]] developer [[Matthew Garrett]] noted that conditions in the [[GNU General Public License#Version 3|GNU General Public License version 3]] may prevent the use of the [[GNU GRUB|GNU GRand Unified Bootloader]] without a distribution's developer disclosing the private key (however, the [[Free Software Foundation]] has since clarified its position, assuring that the responsibility to make keys available was held by the hardware manufacturer),<ref>{{cite web|title=Free Software Foundation recommendations for free operating system distributions considering Secure Boot — Free Software Foundation — working together for free software|url=https://www.fsf.org/campaigns/secure-boot-vs-restricted-boot/whitepaper-web|website=Free Software Foundation|access-date=18 March 2020}}</ref><ref name="h-ubuntusecureboot">{{cite web|title=Ubuntu will use GRUB 2 for its Secure Boot implementation|url=http://www.h-online.com/open/news/item/Ubuntu-will-use-GRUB-2-for-its-Secure-Boot-implementation-1714232.html|publisher=The H Online|access-date=28 October 2012}}</ref> and that it would also be difficult for advanced users to build custom [[Linux kernel|kernels]] that could function with Secure Boot enabled without self-signing them.<ref name="cwuk-arm" /> Other developers suggested that signed builds of Linux with another key could be provided, but noted that it would be difficult to persuade OEMs to ship their computers with the required key alongside the Microsoft key.<ref name="ElReg1">{{cite news|date=23 September 2011|title=MS denies secure boot will exclude Linux|publisher=The Register|url=https://www.theregister.co.uk/2011/09/23/ms_denies_uefi_lock_in/|access-date=24 September 2011}}</ref>
====Disputes====
It has been disputed whether the operating system [[Kernel (computer science)|kernel]] and its modules must be signed as well; while the UEFI specifications do not require it, Microsoft has asserted that their contractual requirements do, and that it reserves the right to revoke any certificates used to sign code that can be used to compromise the security of the system.<ref name="h-mscert">{{cite web|title=No Microsoft certificate support in Linux kernel says Torvalds|url=http://www.h-online.com/open/news/item/No-Microsoft-certificate-support-in-Linux-kernel-says-Torvalds-1811883.html|access-date=26 February 2013|publisher=The H}}</ref> In Windows, only the [[WHQL]] kernel driver is allowed if Secure Boot is enabled. In February 2013, another Red Hat developer attempted to submit a patch to the Linux kernel that would allow it to parse Microsoft's authenticode signing using a master [[X.509]] key embedded in [[Portable Executable|PE]] files signed by Microsoft. However, the proposal was criticized by Linux creator [[Linus Torvalds]], who attacked Red Hat for supporting Microsoft's control over the Secure Boot infrastructure.<ref name="ars-linus">{{cite web|title=Linus Torvalds: I will not change Linux to "deep-throat Microsoft"|date=26 February 2013 |url=https://arstechnica.com/information-technology/2013/02/linus-torvalds-i-will-not-change-linux-to-deep-throat-microsoft/|publisher=Ars Technica|access-date=26 February 2013}}</ref>

== Notes ==
{{Notelist}}

== References ==
{{reflist|30em}}

== Further reading ==

* {{cite web|last1=Zimmer|first1=Vincent|first2=Michael|last2=Rothman|first3=Robert|last3=Hale|title=EFI Architecture|url=http://www.drdobbs.com/embedded-systems/efi-architecture/199500688|work=[[Dr. Dobb's Journal]]|publisher=[[UBM plc|UBM]]|access-date=12 October 2012|date=10 May 2007}}
* {{cite web|first=Jonathan|last=de Boyne Pollard|url=http://jdebp.eu./FGA/efi-boot-process.html|title=The EFI boot process|work=Frequently Given Answers|date=11 July 2011|access-date=12 October 2012}}
* {{cite web|first=Jonathan|last=de Boyne Pollard|url=http://jdebp.eu./FGA/windows-nt-6-boot-process.html|title=The Windows NT 6 boot process|work=Frequently Given Answers|date=8 December 2011|access-date=12 October 2012}}
* {{cite web|first=Roderick W.|last=Smith|url=http://rodsbooks.com/bios2uefi/|title=A BIOS to UEFI Transformation|work=Roderick W. Smith's Web Page|year=2011|access-date=12 October 2012}}
* {{cite web|first=Rajiv|last=Kothari|url=http://www.hardwaresecrets.com/article/UEFI-Just-How-Important-It-Really-Is/1385|title=UEFI – Just How Important It Really Is|work=Hardware Secrets|date=21 September 2011|access-date=12 October 2012|url-status=dead|archive-url=https://web.archive.org/web/20121025093125/http://www.hardwaresecrets.com/article/UEFI-Just-How-Important-It-Really-Is/1385|archive-date=25 October 2012}}
* {{cite journal|last=Fisher|first=Doug|year=2011|title=UEFI Today: Bootstrapping the Continuum|url=http://noggin.intel.com/technology-journal/2011/151/uefi-today-bootstrapping-continuum|journal=Intel Technology Journal|publisher=Intel|volume=15|issue=1|isbn=9781934053430|access-date=24 September 2013|archive-date=27 September 2013|archive-url=https://web.archive.org/web/20130927155448/http://noggin.intel.com/technology-journal/2011/151/uefi-today-bootstrapping-continuum|url-status=dead}}

== Other websites ==
{{Commons category|Extensible Firmware Interface}}

* {{Official website|https://uefi.org/}}
* [https://uefi.org/specifications UEFI Specifications]
* [https://www.tianocore.org/ Intel-sponsored open-source EFI Framework initiative]
* [https://www.intel.com/content/www/us/en/architecture-and-technology/unified-extensible-firmware-interface/efi-homepage-general-technology.html Intel EFI/UEFI portal]
* [https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh824898(v=win.10) Microsoft UEFI Support and Requirements for Windows Operating Systems]
* [https://www.techrepublic.com/blog/windows-and-office/how-windows-8-hybrid-shutdown-fast-boot-feature-works/ How Windows 8 Hybrid Shutdown / Fast Boot feature works]
* [https://docs.microsoft.com/en-us/windows/security/information-protection/secure-the-windows-10-boot-process Securing the Windows 10 Boot Process]
* [https://www.welivesecurity.com/2018/09/27/lojax-first-uefi-rootkit-found-wild-courtesy-sednit-group/ LoJax: First UEFI rootkit found in the wild, courtesy of the Sednit group]
[[Category:Computing]]