Local privilege escalation via arbitrary kernel writes
Published Sep 21, 2026 · Updated Sep 21, 2026
Write-what-where in BIOSTAR VALKYRIE AURORA Utility 2.10.2411.0800 allows local users to overwrite arbitrary kernel memory. The BS_RVSIO64.sys IOCTL handler function sub_1105C uses the caller-controlled PhysicalAddress argument as the destination of a memory write without adequately restricting the target address. Low-privilege local access is required; successful exploitation grants kernel-level memory control and can compromise the host.
Summary
What happened
Write-what-where in BIOSTAR VALKYRIE AURORA Utility 2.10.2411.0800 allows local users to overwrite arbitrary kernel memory. The BS_RVSIO64.sys IOCTL handler function sub_1105C uses the caller-controlled PhysicalAddress argument as the destination of a memory write without adequately restricting the target address. Low-privilege local access is required; successful exploitation grants kernel-level memory control and can compromise the host.
The record
- CVE
- CVE-2026-94129
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- BIOSTAR Microtech International Corp.
- Product
- VALKYRIE AURORA Utility
- Classifications
- CWE-123, CWE-119, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 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=2.10.2411.0800
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- BS_RVSIO64.sys vulnerable-driver samplefunctional · validated
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started