EDK II - NULL Pointer Dereference in XhcPeiInitializeDeviceSlot64

Executive Summary

The PEI-phase 64-bit counterpart of XhcInitializeDeviceSlot. Three allocations lack proper NULL checks: (1) InputContext at line 1337 with ASSERT-only, then ZeroMem at 1340; (2) EndpointTransferRing at line 1398 with NO NULL CHECK AT ALL, passed to XhcPeiCreateTransferRing at 1400; (3) OutputContext at line 1440 with ASSERT-only, then ZeroMem at 1443.

This advisory is one of a set reported to VulnCheck on 2026-06-25 for coordinated disclosure to the EDK II maintainers. After several follow-ups over the following months no response was received. 126 days after the initial report, ByteRay is publishing the findings in good faith so that affected integrators can assess and remediate them. All findings were identified against EDK II commit 70741a15d9a714323a5598eac47727e60507e22f (master, 2026-06-21).

Affected Products and Versions

• Vendor: TianoCore
• Product: EDK II (MdeModulePkg)
• Affected commit: 70741a15d9a714323a5598eac47727e60507e22f (master, 2026-06-21). The code is present on that commit and later revisions that have not changed it.
• Location: MdeModulePkg/Bus/Pci/XhciPei/XhciSched.c:1337
• Function: XhcPeiInitializeDeviceSlot64
• Category: error_handling

Technical Details

Controllability: SEMI_TRUSTED — confidence: high. Physical USB device triggers PEI-phase 64-bit enumeration.

Data Flow

At line 1337, InputContext = UsbHcAllocateMem(...) with ASSERT-only at 1338, then ZeroMem at 1340. At line 1398, EndpointTransferRing = AllocateZeroPool(...) with NO CHECK AT ALL, passed to XhcPeiCreateTransferRing at 1400. At line 1440, OutputContext = UsbHcAllocateMem(...) with ASSERT-only at 1441, then ZeroMem at 1443.

Affected Callers

• XhcPeiPollPortStatusChange

Sanitization / Security Controls

• DEBUG-only ASSERT (partial).

Reachability and Preconditions

Attacker position and trust level for this issue are stated in the Controllability line and Data Flow above, and the concrete trigger is in Reproduction below.

Exploitability: Low
Realism: Low

Reproduction

1. Physical access to USB port; PEI-phase boot; 64-bit XHCI controller; memory pressure.
2. Attacker connects physical USB device during PEI-phase boot.
3. XhcPeiPollPortStatusChange detects the USB connect and calls XhcPeiInitializeDeviceSlot64.
4. At line 1337, UsbHcAllocateMem for InputContext returns NULL; ASSERT at 1338 is no-op; ZeroMem at 1340 dereferences NULL.
5. At line 1398, AllocateZeroPool for EndpointTransferRing returns NULL with NO CHECK; XhcPeiCreateTransferRing at 1400 dereferences NULL

Impact

Denial of service — firmware crash during PEI USB enumeration. All three allocations have fixed sizes, so a USB device only reaches this path; the failure needs PEI memory to be already exhausted.

Remediation and Mitigation

As of commit 70741a15d9a714323a5598eac47727e60507e22f this issue is unfixed upstream and no CVE has been assigned. Check the allocation result for NULL before dereferencing it and fail the operation cleanly when allocation fails. The specific control that is absent or ineffective is identified in the Sanitization / Security Controls list under Technical Details.

Timeline

• 2026-06-25 - Reported to VulnCheck for coordinated disclosure to the TianoCore / EDK II security team.
• 2026-07 to 2026-10 - Several follow-ups sent; no response received.
• 2026-10-29 - Public disclosure in good faith, 126 days after the initial report.

Credits

Discovered and reported by Argus-Systems.

References

• EDK II source (TianoCore)
• Affected file at the referenced commit