CVE-2022-36764 is a high severity (CVSS 7.0) memory safety flaw in Tcg2MeasurePeImage() in TianoCore EDK2, the open source UEFI firmware base. EDK2 releases up to 202311 are affected and the advisory lists no patched release. Apply the vendor patch, or firmware updates from your hardware supplier.
What's affected
The TianoCore GitHub advisory lists the affected component as SecurityPkg in EDK2, affected versions up to and including 202311, and patched versions as None. It states that patch files are available through the TianoCore Bugzilla entry https://bugzilla.tianocore.org/show_bug.cgi?id=4118 and that the fix was planned for the February 2024 EDK2 release. I did not confirm that the release shipped, so check the current EDK2 tree and release notes.
The record scores the flaw 7.0 (High) with vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H: local access, high complexity, low privileges, and a changed scope. The weakness classes are CWE-122 (Heap-based Buffer Overflow) and CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer).
EDK2 is a code base, not a product you install. It sits inside the firmware of many servers, laptops and virtual machine platforms, so the practical question is which firmware builds you run and whether your hardware vendor has merged the fix.
How to check if you're exposed
You will not find EDK2 in a package manager on most machines, so the check is about firmware and virtualization.
- List the hardware and virtual machine platforms in your fleet that boot through UEFI and use TPM measured boot.
- Ask each hardware vendor, or read its security bulletins, for the firmware version that includes the TianoCore fix for Bugzilla 4118.
- If you build your own firmware from EDK2, check whether your source tree includes the fix for Tcg2MeasurePeImage().
On a Linux host you can read the firmware version the machine reports, then compare it with your vendor's bulletin:
sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date
If you run virtual machines with OVMF, the EDK2 based firmware for QEMU and KVM, ask your distribution whether it has backported the fix. Distribution announcements for this CVE exist in the record's references, though I did not read them.
What to do now
- Inventory firmware and virtual machine firmware that is built on EDK2.
- Check vendor bulletins for a firmware update that includes the TianoCore fix referenced by Bugzilla 4118.
- If you maintain your own EDK2 build, apply the patch from the Bugzilla entry or move to an EDK2 release that includes it.
- Limit who can write to the EFI system partition and who can attach untrusted disks or images to machines that matter, since the input comes from disk.
- Re-check after your vendors publish firmware updates, and record the build you end up on.
Why it matters
This function measures a PE image, the format of UEFI executables, into the TPM event log. Its comments say it handles untrusted input. The advisory explains that the code takes the size of the file path, adds it to a fixed structure size, and allocates a buffer, without checking that the sum did not overflow. A very large path size could therefore produce a very small allocation, and the later copy of the path into that buffer runs past its end.
The advisory also traces where the missing check should have lived, in the device path size helper, and notes that responsibility for the check was unclear between the caller and that helper. That is a common pattern behind integer overflows: two functions each assume the other did the checking.
Heap corruption in firmware is serious because it runs before the operating system and its defenses. The record's KEV flag is false and no exploitation is reported.
Quick check
Is this the same bug as the GPT one?
No. It is a sibling issue in the same measured boot library, but a different function, a different Bugzilla entry and a different CVE.
What is the first step for a typical admin?
Find out which of your hardware and virtual machine platforms use EDK2 based firmware, then watch for vendor updates.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.