Kernel code execution via unrestricted physical-memory IOCTLs
Published May 22, 2024 · Updated Mar 13, 2025
Privilege escalation in ASUS ATSZIO Driver 0.2.1.7 allows local users to execute arbitrary code through crafted IOCTL requests. ATSZIO64.sys exposes physical-memory mapping, I/O-port access, and model-specific-register operations through DeviceIoControl without restricting low-privileged callers. Any local low-privileged process can invoke these kernel capabilities to read or modify hardware-backed state and run code with elevated privileges.
Summary
What happened
Privilege escalation in ASUS ATSZIO Driver 0.2.1.7 allows local users to execute arbitrary code through crafted IOCTL requests. ATSZIO64.sys exposes physical-memory mapping, I/O-port access, and model-specific-register operations through DeviceIoControl without restricting low-privileged callers. Any local low-privileged process can invoke these kernel capabilities to read or modify hardware-backed state and run code with elevated privileges.
The record
- CVE
- CVE-2024-33222
- Published
- May 22, 2024
- Updated
- Mar 13, 2025
- Vendor
- ASUSTeK Computer Inc.
- Product
- ASUS ATSZIO Driver
- Classifications
- CWE-782, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 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=0.2.1.7
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
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