Memory corruption via unchecked relocation-bound addition
Published Sep 27, 2024 · Updated Nov 3, 2025
Heap-based buffer overflow in TianoCore EDK II through 202408 allows attackers on an adjacent network to corrupt firmware memory. PeCoffLoaderRelocateImage adds the UINT32 relocation-directory size to its virtual address without checking whether the sum overflows before deriving relocation bounds. Exploitation requires low privileges and adjacent-network reachability; corruption can disclose or alter data or interrupt firmware execution.
Summary
What happened
Heap-based buffer overflow in TianoCore EDK II through 202408 allows attackers on an adjacent network to corrupt firmware memory. PeCoffLoaderRelocateImage adds the UINT32 relocation-directory size to its virtual address without checking whether the sum overflows before deriving relocation bounds. Exploitation requires low privileges and adjacent-network reachability; corruption can disclose or alter data or interrupt firmware execution.
The record
- CVE
- CVE-2024-38796
- Published
- Sep 27, 2024
- Updated
- Nov 3, 2025
- Vendor
- TianoCore
- Product
- EDK II
- Classifications
- CWE-122
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=edk2-stable202405
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo