Pre-boot memory access via failed IOMMU initialization
Published Dec 17, 2025 · Updated Dec 17, 2025
Improper access control in ASUS motherboard UEFI firmware allows physically proximate attackers to read or alter memory before OS defenses load. The firmware reports pre-boot DMA protection as active but fails to configure and enable the IOMMU during the early boot handoff. Physical access to an internal PCIe slot and a DMA-capable device is required; exploitation can expose sensitive memory or inject code before operating-system controls start.
Summary
What happened
Improper access control in ASUS motherboard UEFI firmware allows physically proximate attackers to read or alter memory before OS defenses load. The firmware reports pre-boot DMA protection as active but fails to configure and enable the IOMMU during the early boot handoff. Physical access to an internal PCIe slot and a DMA-capable device is required; exploitation can expose sensitive memory or inject code before operating-system controls start.
The record
- CVE
- CVE-2025-11901
- Published
- Dec 17, 2025
- Updated
- Dec 17, 2025
- Vendor
- ASUSTeK Computer Inc.
- Product
- Z690 Series Motherboards
- Classifications
- CWE-284, 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=before 3810, 4501
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.
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