EDK II - NULL Pointer Dereference in XenBusDxeDriverBindingStart

Executive Summary

In the XenBusDxe driver binding Start function (XenBusDxeDriverBindingStart, line 312), Dev = AllocateZeroPool(sizeof(*Dev)) has NO NULL CHECK before Dev->Signature = XENBUS_DEVICE_SIGNATURE at line 350 dereferences it. Four more field writes follow at lines 351–355. While this is guest-initiated during driver binding, the complete absence of a NULL check means any allocation failure results in a NULL dereference.

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 (OvmfPkg)
• Affected commit: 70741a15d9a714323a5598eac47727e60507e22f (master, 2026-06-21). The code is present on that commit and later revisions that have not changed it.
• Location: OvmfPkg/XenBusDxe/XenBusDxe.c:349
• Function: XenBusDxeDriverBindingStart
• Category: error_handling

Technical Details

Controllability: SYSTEM_CONTROLLED — confidence: high. Constant-size, guest-initiated allocation during driver binding. No external attacker control over the source.

Data Flow

At line 349, Dev = AllocateZeroPool(sizeof(*Dev)) is a constant-size allocation with NO NULL CHECK. At line 350, Dev->Signature = XENBUS_DEVICE_SIGNATURE dereferences NULL. Lines 351–355 perform further field writes that dereference Dev.

Affected Callers

• UEFI driver binding (ConnectController) through gXenBusDxeDriverBinding (XenBusDxe.c:35-37), once per XenIo controller

Sanitization / Security Controls

• None.

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. Memory exhaustion during XenBus driver initialization.
2. XenBusDxeDriverBindingStart is called during driver binding.
3. At line 349, AllocateZeroPool(sizeof(*Dev)) returns NULL on failure.
4. At line 350, Dev->Signature = XENBUS_DEVICE_SIGNATURE dereferences NULL.
5. Lines 351–355 perform further field writes that dereference Dev, crashing the firmware

Impact

Denial of service — firmware crash during XenBus driver initialization.

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