CVE-2025-14302 json
GIGABYTE|Motherboard - Protection Mechanism Failure
published 2025-12-17 10 mo ago modified 2026-10-07 33 d ago also EUVD-2025-203865
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 10 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.0 | 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 |
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 7.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- GIGABYTE intel 600 chipset Motherboard
- GIGABYTE intel 700 chipset Motherboard
- GIGABYTE intel 800 chipset Motherboard
- GIGABYTE AMD 600 chipset motherboard
- GIGABYTE AMD 800 chipset motherboard
- GIGABYTE AMD TRX50 chipset motherboard
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
gigabyte.com
/Support/Security?type=1
vendor-advisory
-
twcert.org.tw
/tw/cp-132-10574-ddf09-1.html
third-party-advisory
-
twcert.org.tw
/en/cp-139-10575-e4f41-2.html
third-party-advisory
Sources
- CVE List CVE-2025-14302
- NVD CVE-2025-14302
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.