ASRock Motherboards
CVE-2025-14304
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to system
-
DeliveryAttach DMA-capable PCIe device
-
ExploitExploit missing IOMMU protection pre-boot
-
ExecutionRead/write arbitrary physical memory
-
ImpactExtract keys or bypass OS security
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 machine and a DMA-capable PCIe (or Thunderbolt/PCIe-tunneling) device, exploitable specifically during the pre-boot window before the OS kernel and its security features (and any OS-level IOMMU/DMA remapping) are initialized. The root cause is that IOMMU/DMA protection is not properly enabled in firmware on the affected 'certain' ASRock, ASRockRack, and ASRockInd motherboard models. Limiting factors: attack vector is physical (AV:P) - no remote or network path exists; the exploit window closes once a correctly-configured OS enables its own IOMMU protection; and only specific, unenumerated board models are vulnerable. |
| Impact | This is a physical-access DMA attack, and the CVSS 4.0 vector (AV:P/AC:L/AT:N/PR:N/UI:N, VC:H/VI:H/VA:H, score 7.0) is the dominant signal: exploitation requires the attacker to be physically present at the machine to attach a DMA-capable PCIe device, which sharply constrains real-world scalability despite the high technical impact (full arbitrary read/write of physical memory). Supporting signals all point to low urgency: EPSS is 0.35% (26th percentile), there is no CISA KEV listing, and no public exploit was identified at time of analysis - consistent with a hardware-firmware weakness rather than a remotely-scriptable flaw. The signals are coherent rather than conflicting: a genuinely high-impact primitive (pre-boot memory access defeating OS security features) gated behind a physical-presence requirement. The one metadata conflict is the 'Information Disclosure' tag, which understates the issue - the description explicitly states arbitrary read AND write of physical memory, i.e. full integrity and availability impact, not just confidentiality. Net: a legitimate high-severity issue for threat models that include physical access, supply-chain interception, or 'evil maid' scenarios, but not a mass-exploitation priority. |
| Exploit ScenarioDerived | An attacker with brief physical access to a vulnerable ASRock motherboard (e.g. an evil-maid or supply-chain interception scenario) inserts a DMA-capable PCIe/Thunderbolt device before the OS boots. Because IOMMU is not properly enabled at that stage, the device performs arbitrary reads and writes of physical memory, extracting secrets (disk-encryption keys, credentials) or patching memory to defeat Secure Boot and OS security features. No public exploit code was identified, but generic PCIe-DMA tooling (e.g. PCILeech-class devices) makes this class of attack well-understood. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Motherboards from ASRock, ASRockRack, and ASRockInd ship with IOMMU/DMA remapping not properly enabled in firmware, allowing an attacker with physical access to plug in a DMA-capable PCIe device and read or write arbitrary physical memory during the pre-boot window, before the OS kernel and its security features are loaded. Exploitation requires hands-on physical presence at the machine (CVSS 4.0 AV:P, base score 7.0; independent assessment CVSS 3.1 AV:P/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact), so although the technical impact is total memory compromise, the attack does not scale remotely and is limited to the specific board models the vendor lists. No public exploit code has been identified at time of analysis, EPSS is low at 0.35% (26th percentile), and there is no CISA KEV listing indicating confirmed active exploitation, but the affected board list is not fully enumerated in the available advisories and the pre-boot window closes only if a correctly configured OS enables its own IOMMU protection.
RemediationAI
No exact patched BIOS/firmware version is identified in the available data, so the primary action is to consult the vendor advisories - https://www.asrock.com/support/Security.asp and https://www.asrockind.com/zh-tw/security-center, plus the TWCERT bulletin at https://www.twcert.org.tw/en/cp-139-10579-9205b-2.html - and apply the model-specific BIOS/UEFI update that corrects the IOMMU/DMA-remapping configuration; treat this as a firmware fix rather than an OS-side patch. As an immediate compensating control, enter UEFI setup and explicitly enable Intel VT-d / AMD-Vi (IOMMU) and its DMA protection, since the failure is that the mechanism is not properly turned on; the trade-off is that some older add-in cards, RAID controllers, or passthrough configurations may fail to initialize with strict DMA remapping active, so validate workloads after enabling it. Where the port is not needed, disable Thunderbolt/PCIe tunneling and unused PCIe slots in firmware, set a BIOS administrator password, and disable pre-boot external device boot and DMA-capable port access, accepting that this reduces legitimate hot-plug and dock usability. Finally apply physical security controls - locked chassis with intrusion detection, tamper-evident seals, and restricted physical access to servers and industrial systems - since the attack requires an attacker to be physically present with a DMA-capable device during the pre-boot window; note these controls reduce opportunity but do not eliminate the underlying firmware misconfiguration, which is why the vendor firmware fix remains required.
Affected ProductsAI
The vulnerability affects specific, unenumerated motherboard models from ASRock and its subsidiaries ASRockRack (server boards) and ASRockInd (industrial boards). The available data does not provide CPE strings or a version-range table, and the vendor advisories describe the affected set only as 'certain motherboard models', so administrators must match their exact board model and BIOS revision against the vendor lists at https://www.asrock.com/support/Security.asp, https://www.asrockind.com/zh-tw/security-center, and the TWCERT advisories at https://www.twcert.org.tw/en/cp-139-10579-9205b-2.html (English) and https://www.twcert.org.tw/tw/cp-132-10578-c43b4-1.html (Chinese). Because the disclosure originates from TWCERT and carries the 'Information Disclosure' tag, the coverage of affected models may expand as the vendor publishes model-specific firmware guidance.
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 root cause is classed as CWE-693, Protection Mechanism Failure: the platform's intended DMA protection mechanism, the IOMMU (Intel VT-d or AMD-Vi), is not correctly enabled or configured in the affected motherboard firmware. IOMMU is what restricts a PCIe device's DMA engine to the memory regions the OS has explicitly mapped for it; when it is off or misconfigured prior to OS handoff, any bus-mastering device can issue DMA transactions against arbitrary physical addresses. The practical exploitation vector is a DMA-capable PCIe or Thunderbolt/PCIe-tunneling device attached to an exposed slot or port, used during the firmware/pre-boot phase when no OS-level DMA remapping or kernel page protections are in force. The CVSS 4.0 vector AV:P/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H confirms the attacker needs physical access but no authentication or user interaction, and achieves complete compromise of the memory-resident confidentiality, integrity, and availability of the host - hence full physical memory read/write, which enables credential theft, firmware/secure-boot manipulation, or hypervisor-level tampering. EPSS 0.35% and the low-severity percentile reflect the strong physical-access precondition rather than a lack of impact.
Know when Asrock 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 access with DMA hardware (AV:P) and no auth/UI needed (PR:N/UI:N) yields full arbitrary memory read/write (C:H/I:H/A:H); scope unchanged as impact stays within the target host.
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
DescriptionCVE.org
Certain motherboard models developed by ASRock and its subsidiaries, ASRockRack and ASRockInd. 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
ASRock, ASRockRack, and ASRockInd motherboards contain a firmware security gap that lets someone with physical access compromise system memory before the operating system starts, creating a high-severity exposure for organizations that operate these boards in physically accessible locations. The issue is not remotely scalable and no public exploit identified at time of analysis, so leadership should focus on inventory, physical security, and vendor firmware tracking rather than broad emergency remote patching. Affected teams include data center operations, labs, kiosks, and any site where these boards are not behind strong physical controls.
No vendor-released patch identified at time of analysis. Interim mitigations: enable IOMMU/DMA remapping in UEFI/firmware where supported; enforce physical access controls (locked racks, badge access, surveillance); disable unused PCIe slots; use chassis intrusion detection and tamper-evident seals; monitor ASRock, ASRockRack, and ASRockInd advisories for board-specific firmware updates.
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 AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Str
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Str
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Str
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Str
Authenticated local attackers on Windows systems running ASRock Polychrome SYNC/RGB can crash the operating system by su
ASRock Polychrome SYNC/RGB kernel driver improperly restricts I/O port access via its IOCTL interface, allowing any auth
AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as demonstrated by triggering
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB