Physical memory read and write via uninitialized IOMMU
Published Dec 17, 2025 · Updated Dec 17, 2025
Protection mechanism failure in GIGABYTE motherboard UEFI firmware allows physically proximate attackers to read or write physical memory. The firmware can report DMA protection as active while leaving the IOMMU incorrectly configured during early boot. Physical access and a DMA-capable PCIe device are required, and access occurs before the operating system kernel and its security controls load.
Summary
What happened
Protection mechanism failure in GIGABYTE motherboard UEFI firmware allows physically proximate attackers to read or write physical memory. The firmware can report DMA protection as active while leaving the IOMMU incorrectly configured during early boot. Physical access and a DMA-capable PCIe device are required, and access occurs before the operating system kernel and its security controls load.
The record
- CVE
- CVE-2025-14302
- Published
- Dec 17, 2025
- Updated
- Dec 17, 2025
- Vendor
- GIGA-BYTE Technology Co., Ltd.
- Product
- GIGABYTE AMD 800 Series Motherboards
- Classifications
- CWE-693, CAPEC-401, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 17, 2025CVE publishedPublication date reported by the CVE source.
- Dec 17, 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
What conditions does exploitation require?
What is affected?
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