Recovering an information handling system from a secure boot authentication failure

An information handling system (IHS) comprising:

• a first IHS component having a first memory device;
• and
• a processor communicatively coupled to a second memory device, the processor further communicatively coupled to the first IHS component and the first memory device, the processor having firmware executing thereon for recovering the IHS from a secure boot authentication failure, wherein the firmware configures the processor to:
• retrieve from the first memory device during a boot operation of the IHS, a current first unified extensible firmware interface (UEFI) driver associated with a first component/device of the IHS;
• in response to a secure boot process being enabled during a driver execution environment (DXE) phase of the boot operation, determine, via the secure boot process, if the first UEFI driver is an authenticated UEFI driver, the secure boot process comprising using a set of public keys stored in firmware to authenticate the first UEFI driver, and the secure boot process preventing a loading of drivers or images that are not signed with an acceptable digital signature;
• in response to determining that the first UEFI driver is an authenticated driver, load the first UEFI driver, wherein if the secure boot process is not enabled, an authentication check of the UEFI driver is not performed during the DXE phase prior to loading the UEFI driver;
• in response to determining that the first UEFI driver is not an authenticated UEFI driver, retrieve a previously validated UEFI driver corresponding to the first component/device and loading the previously validated UEFI driver;
• determine if a current validated UEFI driver is to be updated with a new validated UEFI driver;
• and
• in response to a current validated UEFI image and/or driver being updated:
• receive new UEFI images and drivers;
• determine if the received UEFI image and/or UEFI driver are authentic using a secure boot process;
• and in response to all of the new UEFI images and drivers being authenticated, identify the new UEFI images and drivers as known new valid UEFI images and drivers.

A recovery system for recovering an information handling system (IHS) from a secure boot authentication failure, the recovery system comprising:

• a first IHS component having a first non-volatile memory device;
• and
• a processor communicatively coupled to a second memory device, the processor further communicatively coupled to the first IHS component and the first non-volatile memory device, the processor having firmware executing thereon for recovering the IHS from a secure boot authentication failure, wherein the firmware configures the processor to:
• retrieve from the first non-volatile memory device during a boot operation, a current first unified extensible firmware interface (UEFI) driver associated with the first component of the IHS;
• in response to a secure boot process being enabled during a driver execution environment (DXE) phase of the boot operation, determine, via the secure boot process, if the first UEFI driver is an authenticated UEFI driver, the secure boot process comprising using a set of public keys stored in firmware to authenticate the first UEFI driver, and the secure boot process preventing a loading of drivers or images that are not signed with an acceptable digital signature;
• in response to determining that the first UEFI driver is an authenticated driver, load the first UEFI driver, wherein if the secure boot process is not enabled, an authentication check of the UEFI driver is not performed during the DXE phase prior to loading the UEFI driver;
• in response to determining that the first UEFI driver is not an authenticated UEFI driver, retrieve a previously validated UEFI driver corresponding to the first component/device and loading the previously validated UEFI driver;
• determine if a current validated UEFI driver is to be updated with a new validated UEFI driver;
• and
• in response to a current validated UEFI image and/or driver being updated:
• receive new UEFI images and drivers;
• determine if the received UEFI image and/or UEFI driver are authentic using a secure boot process;
• and in response to all of the new UEFI images and drivers being authenticated, identify the new UEFI images and drivers as known new valid UEFI images and drivers.