microsoft/mu_basecore v2025020002.0.1

v2025020002.0.1

Repository: microsoft/mu_basecore

Tag: v2025020002.0.1

Published: 2025-10-14T03:32:26Z

Prerelease: no

Release notes:

What's Changed

[FF-A] Update Header to Include FFA\_NS\_RES\_INFO\_GET @Raymond-MS (#1520)

Change Details

Description

Add FFA_NS_RES_INFO_GET to the ARM FF-A header.

For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

• [ ] Impacts functionality?
• [ ] Impacts security?
• [ ] Breaking change?
• [ ] Includes tests?
• [ ] Includes documentation?

How This Was Tested

Verified through QemuSbsa build and FfaPartitionTestApp.

Integration Instructions

N/A

[CHERRY-PICK] workflow: Update BaseTool extdep weekly @Javagedes (#1516)

Change Details

Description

Creates a new recurring workflow that runs weekly. This workflow finds all releases that occurred in the last 7 days, and finds the most recent release for each associated branch (e.g. if three releases happened [v202502000.0.1, dev-v202502000.0.1, v202502000.0.2], we reduce that to only [v202502000.0.2', 'dev-v202502000.0.1'] because two of them target the same release/202502 branch).

If we do not find any releases, we abort early. Otherwise for each release, we will create a PR for the specific branch, updating the base tools extdep to the most recent release. If a PR already exists for an older version, we will close it.

Cherry-pick of #1383

An additional commit after this cherry-pick is applied to remove the dev branch logic.

• [ ] Impacts functionality?
• [ ] Impacts security?
• [ ] Breaking change?
• [ ] Includes tests?
• [ ] Includes documentation?

How This Was Tested

N/A

Integration Instructions

N/A

[Cherry-Pick] NetworkPkg/UefiPxeBcDxe: Add buffer check before reporting status code @apop5 (#1517)

Change Details

Description

When PxeBcLoadBootFile() fails, it reports a status code to notify listeners (such as telemetry/SEL logging drivers) about the error. However, the current implementation reports the status code for all error conditions, including benign cases, such as where the caller passes Buffer == NULL with EFI_BUFFER_TOO_SMALL to query the required size.

This causes false positive error reports in telemetry systems, as EFI_BUFFER_TOO_SMALL with Buffer == NULL is an expected and normal operation for size queries, not an actual error condition.

The PXE-E05 error message is already correctly guarded with the condition "(Status == EFI_BUFFER_TOO_SMALL) && (Buffer != NULL)", but the status code reporting was unconditional.

Add a buffer null check before REPORT_STATUS_CODE_WITH_EXTENDED_DATA to ensure status codes are only reported for actual errors:

• Report when Status != EFI_BUFFER_TOO_SMALL (all other errors)
• Report when Status == EFI_BUFFER_TOO_SMALL AND Buffer != NULL (PXE-E05)
• Skip when Status == EFI_BUFFER_TOO_SMALL AND Buffer == NULL (size query)

This prevents spurious error logs while maintaining proper error reporting for genuine failures including PXE-E05, PXE-E07, PXE-E09, PXE-E99, and all other error conditions.

(cherry picked from commit d3a64baf4b6706367c30a4886c01e95589861c9f)

• [x] Impacts functionality?
• [ ] Impacts security?
• [ ] Breaking change?
• [ ] Includes tests?
• [ ] Includes documentation?

How This Was Tested

PXE booting physical platform. After change, no longer encounter double status code listener error report.

Integration Instructions

No integration necessary.

MockPolicyLibCommon : Add SetPolicy @Irene-IY (#1512)

Change Details

Description

Add SetPolicy into MockPolicyLibCommon

Signed-off-by : Irene-IY

• [ ] Impacts functionality?
• [ ] Impacts security?
• [ ] Breaking change?
• [ ] Includes tests?
• [ ] Includes documentation?

How This Was Tested

CI test

Integration Instructions

N/A

[CHERRY-PICK] MdePkg: Add MockSpiNorFlashProtocol @PaddyDengAmi (#1507)

Change Details

Description

Add MockSpiNorFlashProtocol for google test components to use.

• [ ] Impacts functionality?
• [ ] Impacts security?
• [ ] Breaking change?
• [ ] Includes tests?
• [ ] Includes documentation?

How This Was Tested

Consumed by other google test

Integration Instructions

N/A

[REBASE \& FF] Prevent AP GP Fault @os-d (#1515)

Change Details

Description

This PR reverts a MU CHANGE to prevent the AP deadlock with a spinlock. This was later determined to not be necessary and instead separate a GDT/TSS is used for each AP, in addition to forcing a graceful transition to those.

This PR also reverts and reapplies a MU_CHANGE as part of that MU_CHANGE was moved to the above new commit and will be upstreamed to edk2 separately. In addition, another piece of this memory protections MU_CHANGE was already changed in https://github.com/microsoft/mu_basecore/commit/2e259b70bc1b100fbb95ecba3651b523f489810b, so that is also dropped.

• [x] Impacts functionality?
• [ ] Impacts security?
• [ ] Breaking change?
• [ ] Includes tests?
• [ ] Includes documentation?

How This Was Tested

Tested on physical Intel client and server platforms that were experiencing the AP deadlock.

Integration Instructions

N/A.

Full Changelog: https://github.com/microsoft/mu_basecore/compare/v2025020002.0.0...v2025020002.0.1