GIGABYTE Motherboards
CVE-2025-14302
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain brief physical access to target
-
DeliveryAttach DMA-capable PCIe device
-
ExploitIssue DMA before IOMMU enabled
-
ExecutionRead/write arbitrary physical memory
-
ImpactExtract secrets or implant boot code
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Requires physical access to the target device and a DMA-capable PCIe (or PCIe-tunneled, e.g. Thunderbolt) device, exploited during the pre-boot window before the OS kernel enables IOMMU/DMA remapping. The core precondition is the affected firmware configuration where IOMMU is not properly enabled early in boot on specific GIGABYTE motherboard models. Limiting factors: exploitation is impossible remotely (AV:P), requires proximity and hands-on hardware attachment, and the memory-access window closes once the OS kernel loads and establishes IOMMU protections; risk is concentrated on unattended, shared, or physically exposed machines. |
| Impact | This is a genuine hardware protection-mechanism failure (CWE-693) but its real-world risk is bounded almost entirely by the physical attack vector. The vendor CVSS 4.0 vector (AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H, 7.0) is internally consistent with the description: an unauthenticated attacker with physical access uses a DMA-capable PCIe device to read and write arbitrary physical memory during the pre-boot window, before IOMMU/OS kernel protections are established. Low complexity and no privileges/interaction required are accurate once physical access is obtained, but AV:P is the dominant limiter - this cannot be exploited remotely or over a network. EPSS is low (0.35%, 26th percentile), there is no CISA KEV listing, and no public exploit code was identified, which together indicate no evidence of opportunistic or widespread exploitation - consistent with a physical/evil-maid class issue rather than a mass-exploited one. Note the signals are not conflicting here: low EPSS, absence of KEV, and a physical vector all point the same direction. This is a real firmware/platform-security weakness worth patching on affected boards, but it is NOT a drop-everything remote priority; prioritize it for high-value, physically exposed, or unattended devices (kiosks, lab machines, laptops-in-transit-equivalent desktops). |
| Exploit ScenarioDerived | An attacker with brief physical access to a powered or booting machine using an affected GIGABYTE motherboard attaches a malicious DMA-capable PCIe/Thunderbolt-attached device. Because IOMMU is not enabled in the pre-boot phase, the device performs direct memory reads and writes to arbitrary physical memory before the OS kernel and its protections load, allowing extraction of secrets or injection of code into early boot. No public exploit code was identified, though the technique mirrors well-documented pre-boot DMA attacks. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Pre-boot DMA attacks against certain GIGABYTE motherboard models can read and write arbitrary physical memory because the IOMMU is not properly enabled before the operating system kernel loads. The flaw is CWE-693 (Protection Mechanism Failure) and requires the attacker to be physically present with a DMA-capable PCIe device - including PCIe-tunneled peripherals such as Thunderbolt - so exploitation cannot be performed remotely and is confined to the window between power-on and kernel initialization of DMA remapping; per the CVSS 4.0 vector the attacker is unauthenticated (PR:N) but the attack vector is physical (AV:P), and impact is high for confidentiality, integrity and availability of the exposed system only. No public exploit code has been identified at time of analysis, there is no CISA KEV listing, and the EPSS score is low at roughly 0.35% (26th percentile), so real-world risk is concentrated on unattended, shared, or physically exposed machines rather than on typical endpoints.
RemediationAI
GIGABYTE addresses this class of issue through firmware/BIOS updates and configuration guidance published on its security page (https://www.gigabyte.com/Support/Security?type=1), with the corresponding TWCERT/CC advisories at https://www.twcert.org.tw/en/cp-139-10575-e4f41-2.html and https://www.twcert.org.tw/tw/cp-132-10574-ddf09-1.html - check those pages for the exact BIOS version applicable to your board model, since the input data does not provide a specific fix version number; patch availability is per vendor advisory rather than a confirmed released build. Where an updated BIOS is not yet applied, the effective compensating control is to enable IOMMU/DMA remapping in firmware setup (Intel VT-d or AMD-Vi, sometimes labelled IOMMU, and the associated pre-boot DMA protection option), which closes the pre-kernel window but can alter device passthrough behaviour for virtualisation and may need to be re-validated against attached hardware. Additional hardening with clear trade-offs includes setting Thunderbolt/USB4 security to require user authorisation, disabling unused PCIe slots and external-PCIe/Thunderbolt controllers in firmware, and applying physical controls such as locked chassis, port blocking and restricted physical access - each reduces the physical DMA attack surface but degrades legitimate hot-plug and expansion use cases, and none substitute for a corrected BIOS. Because the vector is AV:P with no remote component, network-layer controls such as firewalls or segmentation provide no protection against this issue.
Affected ProductsAI
The issue affects certain motherboard models developed by GIGABYTE, identified by GIGABYTE and Taiwan's TWCERT/CC as having a firmware configuration in which the IOMMU is not properly enabled prior to operating-system kernel load; the reference data does not enumerate specific model numbers or firmware revisions, so the authoritative affected-model list must be taken from the vendor security page at https://www.gigabyte.com/Support/Security?type=1 and from the TWCERT/CC advisories at https://www.twcert.org.tw/en/cp-139-10575-e4f41-2.html and https://www.twcert.org.tw/tw/cp-132-10574-ddf09-1.html. No CPE identifiers were supplied in the input data, so affected scope cannot be additionally narrowed via CPE matching, and users of GIGABYTE boards should check the vendor advisory for their exact model and BIOS revision rather than assuming blanket coverage of the product line.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability sits in the platform's memory-protection architecture rather than in application code: on x86 systems the IOMMU (Intel VT-d or AMD-Vi) provides DMA remapping so that a peripheral can only address memory regions explicitly mapped to it. When that translation is not active early in boot, any bus-mastering PCIe endpoint - a malicious expansion card, a rogue Thunderbolt/USB4 device, or an external-PCIe adapter used by a physically present attacker - can issue DMA cycles against arbitrary physical addresses, effectively bypassing the OS kernel's page-table protections and any later-loaded security features, because those protections are established only after the kernel initializes DMA remapping. The CWE-693 classification reflects a failure of an intended protection mechanism (the pre-boot firmware configuration that should enable IOMMU/DMA remapping on these GIGABYTE boards) rather than a memory-corruption bug or a software logic error. Practically, this makes the exposure a firmware/platform hardening issue with a physical prerequisite: the attacker needs hands-on attachment of DMA-capable hardware and must act before the kernel closes the window, after which IOMMU protections come into force.
Know when Gigabyte gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Physical PCIe/DMA access (AV:P) with no auth or interaction (PR:N/UI:N); arbitrary physical memory read and write yields full C:H/I:H/A:H within the affected host (S:U).
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
DescriptionCVE.org
Certain motherboard models developed by GIGABYTE has a Protection Mechanism Failure vulnerability. Because IOMMU was not properly enabled, unauthenticated physical attackers can use a DMA-capable PCIe device to read and write arbitrary physical memory before the OS kernel and its security features are loaded.
Executive ViewAI
Certain GIGABYTE motherboard models are affected by CVE-2025-14302, a pre-boot DMA vulnerability that allows an unauthenticated attacker with physical access and a DMA-capable PCIe device to read and write arbitrary memory before the operating system loads, compromising the confidentiality, integrity, and availability of the exposed system. No public exploit has been identified at time of analysis, and no vendor-released patch is currently available. Risk is concentrated on unattended, shared, or physically exposed machines, so leadership should prioritize physical security and BIOS-level mitigations for those systems.
No vendor-released patch identified at time of analysis. Interim mitigations include enforcing strict physical security (locked cases, restricted access to exposed systems), disabling Thunderbolt and unused PCIe hotplug ports in BIOS/UEFI, enabling IOMMU/VT-d and pre-boot DMA protection in BIOS/UEFI if available, and using port blockers or epoxy on exposed ports.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING
The GPCIDrv and GDrv low-level drivers in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, X
The GDrv low-level driver in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING
The GPCIDrv and GDrv low-level drivers in GIGABYTE APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, X
Remote code execution and privilege escalation in Gigabyte Control Center allows unauthenticated network attackers to wr
Local privilege escalation in the MBStorage DRAM lighting control module of GIGABYTE's Gigabyte Control Center (GCC) let
Insecure deserialization in Gigabyte Control Center's Performance Library component allows authenticated local users to
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB