Tianocore/edk2.git/MdeModulePkg, branch master

MdeModulePkg/UefiHiiLib: Fix memory leaks in ValidateQuestionFromVfr

2026-09-25T12:42:52+00:00

QuestionName is allocated by HiiGetString() but is not released in several code path. This causes memory leaks whenever these paths are taken. Add FreePool (QuestionName) after it is no longer needed. No functional change intended. Signed-off-by: Qihang Gao

MdeModulePkg/SetupBrowserDxe: Fix memory leak in GetQuestionDefault()

2026-09-25T12:42:52+00:00

StrValue is obtained from HiiGetString(), which allocates a new string buffer. The buffer is used to set DefaultValue->Buffer but is never released, causing a memory leak each time this code path is executed. Add FreePool (StrValue) after it is no longer needed. No functional change intended. Signed-off-by: Qihang Gao

MdeModulePkg: Variable: Log Reclaim() completion status

2026-09-21T07:23:22+00:00

Adds a DEBUG_INFO message when Reclaim() finishes so platform boot logs show whether reclaim ran and what status it returned. This makes it easier to distinguish reclaims impact on boot measurements. Signed-off-by: Abdul Lateef Attar

MdeModulePkg/UsbBusDxe: Raise TPL to CALLBACK for wanted UsbIo connect

2026-09-21T06:06:06+00:00

Raise TPL to TPL_CALLBACK around the ConnectController() call in UsbBusRecursivelyConnectWantedUsbIo() and restore the original TPL afterward. UsbBusRecursivelyConnectWantedUsbIo() is normally reached through the DriverBinding Start routine invoked by gBS->ConnectController(), which runs at TPL_APPLICATION. While the wanted UsbIo handle is being connected, the USB device can be removed. The device removal polling event in UsbBus runs at TPL_CALLBACK. If the connect runs at TPL_APPLICATION, that event can preempt the connection and cause commands to be sent to a stale or non-existent USB device address, producing a lot of timeout transfers. This differs from UsbConnectDriver(), which is called from the enumeration polling event (XHCI async event) and is usually already at TPL_CALLBACK or TPL_NOTIFY. That function uses RestoreTPL()/ RaiseTPL() to ensure ConnectController() runs at TPL_CALLBACK. Signed-off-by: Marlboro_Chuang

MdeModulePkg/UsbBusDxe: Handle a quirk in Interface descriptor

2026-09-21T04:54:36+00:00

Some specific device requires a quirk in the Interface descriptor for InterfaceNumber to work properly [Suggested Solution] Implement the mechanism to ensure the first InterfaceNumber not equal to zero. Signed-off-by: Marlboro_Chuang

MdeModulePkg: Add EFIAPI to GptLib functions

2026-09-18T17:02:19+00:00

EFIAPI is required on library interface functions to ensure that the correct calling convention is used. Signed-off-by: Michael Kubacki

MdeModulePkg: Update UI strings to indicate case-insensitive key options

2026-09-15T03:00:02+00:00

Update the prompt strings for save/exit and confirm actions to show both uppercase and lowercase key options (e.g., 'Y(y)' and 'N(n)') to make it clear that the system accepts either case. This improves user experience by avoiding confusion about case sensitivity. Affected strings: - ARE_YOU_SURE (CustomizedDisplayLib) - CONFIRM_OPTION (DisplayEngineDxe) - RECONNECT_CHANGES_OPTIONS (DisplayEngineDxe) French translations are updated accordingly. Signed-off-by: Qihang Gao

MdeModulePkg: Report EFI_SW_DXE_BS_PC_BOOT_OPTION_COMPLETE

2026-09-07T07:37:40+00:00

Previously EfiBootManagerBoot reported EFI_SW_DXE_BS_EC_BOOT_OPTION_FAILED when a boot option returned an error, but reported nothing on success. Report the PI 1.10 status code EFI_SW_DXE_BS_PC_BOOT_OPTION_COMPLETE when a boot option loads, executes, and returns success, so status code listeners can tell that a boot option was attempted and that control returned to firmware. Signed-off-by: Sachin Ganesh

MdeModulePkg/MonotonicCounterRuntimeDxe: Add VarPolicy to the MTC variable

2026-09-03T17:41:04+00:00

Applies a UEFI variable policy to the "MTC" variable to ensure that it is the size of a UINT32 and the variable attributes are restricted to BS, RT, and NV. A protocol dependency on the Variable Policy Protocol is not added to the driver's dependency expression to allow it to be dispatched in firmware that does not have the Variable Policy Protocol installed. Co-authored-by: Michael Kubacki Signed-off-by: Michael Kubacki

MdeModulePkg: DxeIpl: Don't Duplicate Mem Alloc Hob for Stack

2026-09-03T09:00:37+00:00

Currently, DxeIpl will allocate memory for the new DXE stack, which creates a memory allocation HOB for that region. It will then call UpdateStackHob() to find the stack HOB with the old stack info and update the memory address/length to correspond to the new stack. It then creates a new memory allocation HOB for the old stack region as it needs to remain mapped. This ends up creating two memory allocation HOBs for the new stack: a regular memory allocation HOB for the AllocatePages() call and then the stack HOB (which is a memory allocation HOB with a special name). When DXE Core ingests these, it will ignore one of the two HOBs when it goes to allocate memory. However, this is incorrectly describing handoff state. There never should be overlapping memory allocation HOBs. This commit updates DxeIpl behavior to instead find the old stack HOB, convert it to a regular memory allocation HOB, then find the memory allocation HOB for the new stack range and convert it into the stack HOB. Signed-off-by: Oliver Smith-Denny