Local physical-memory read/write via stale whitelist entries
Published May 29, 2026 · Updated May 29, 2026
Incorrect permission assignment in the Armoury Crate 6.4.12 and earlier AsIO3.sys driver allows local users to read and write physical memory. AsIO3.sys permits low-privileged callers to open its device, and its free-memory IOCTL releases pages without deleting their whitelist entries. The stale entries preserve read/write access after Windows recycles the pages, exposing or altering host physical memory without administrator rights.
Summary
What happened
Incorrect permission assignment in the Armoury Crate 6.4.12 and earlier AsIO3.sys driver allows local users to read and write physical memory. AsIO3.sys permits low-privileged callers to open its device, and its free-memory IOCTL releases pages without deleting their whitelist entries. The stale entries preserve read/write access after Windows recycles the pages, exposing or altering host physical memory without administrator rights.
The record
- CVE
- CVE-2026-8070
- Published
- May 29, 2026
- Updated
- May 29, 2026
- Vendor
- ASUSTeK Computer Inc.
- Product
- Armoury Crate
- Classifications
- CWE-732, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 29, 2026CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record 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 <=6.4.12
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.
Weakness, pattern, technique
Public exploit references
- AsIO3.sys stale-whitelist physical-memory PoCproof of concept · demonstrated
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