Kernel information disclosure via unprivileged IOCTL access
Published Mar 12, 2026 · Updated Mar 12, 2026
Incorrect permission assignment in ASUS Business System Control Interface before 0.5.14.0 allows local users to disclose kernel information. The Windows driver exposes an IOCTL request path to unprivileged callers without permissions that protect sensitive hardware resources. Local code execution is required; a crafted IOCTL grants unauthorized hardware access and kernel-information disclosure, with no reported write or availability impact.
Summary
What happened
Incorrect permission assignment in ASUS Business System Control Interface before 0.5.14.0 allows local users to disclose kernel information. The Windows driver exposes an IOCTL request path to unprivileged callers without permissions that protect sensitive hardware resources. Local code execution is required; a crafted IOCTL grants unauthorized hardware access and kernel-information disclosure, with no reported write or availability impact.
The record
- CVE
- CVE-2025-15037
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- ASUSTeK Computer Inc.
- Product
- ASUS Business System Control Interface
- Classifications
- CWE-732
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 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 <0.5.14.0
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