Arbitrary kernel memory write via PhysicalAddress IOCTL
Published Sep 21, 2026 · Updated Sep 21, 2026
Write-what-where in BioStar Temperature Monitor Utility 1.2.1806.2200 allows local users to alter arbitrary physical memory. The BS_HWMIO64_W10.sys sub_1105C IOCTL handler uses the caller-controlled PhysicalAddress without sufficient validation, creating an arbitrary-write primitive. Low-privileged local access is required, and successful exploitation grants arbitrary kernel memory read and write.
Summary
What happened
Write-what-where in BioStar Temperature Monitor Utility 1.2.1806.2200 allows local users to alter arbitrary physical memory. The BS_HWMIO64_W10.sys sub_1105C IOCTL handler uses the caller-controlled PhysicalAddress without sufficient validation, creating an arbitrary-write primitive. Low-privileged local access is required, and successful exploitation grants arbitrary kernel memory read and write.
The record
- CVE
- CVE-2026-94142
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- BIOSTAR Microtech International Corp.
- Product
- Temperature Monitor Utility
- Classifications
- CWE-119, CWE-123, 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=1.2.1806.2200
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
- Arbitrary Kernel Memory Read/Write proof of conceptproof of concept · unverified
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