Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local user-level shell
-
DeliveryOpen handle to DirectIo64.sys device
-
ExploitIssue write IOCTL with zero targeting IA32_LSTAR MSR
-
ExecutionNext system call dereferences null entry point
-
ImpactImmediate unrecoverable kernel crash
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Exposed IOCTL with insufficient ACL
|
| Exploitation Conditions | A local, authenticated Windows user-level account (standard, non-admin) is required - no elevated privileges are needed. The vulnerable DirectIo64.sys driver must be installed and loaded, which occurs as a side effect of installing any of the three affected PassMark products. No special configuration beyond installation is needed; the driver loads automatically with the product. The DoS primitive (MSR zeroing) takes effect on the next system call by any process on the system after the IOCTL is issued, meaning the crash is immediate and affects all users. The MSR read path similarly requires only a handle to the driver device. Exploitation is limited to Windows hosts with one of the three PassMark products installed; the driver is not present by default on any Windows version. |
| Impact | The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H) scores 6.9, accurately reflecting that exploitation requires local authenticated access (PR:L) but imposes no other preconditions. The VA:H rating is well-founded: zeroing the LSTAR MSR causes an immediate, unrecoverable kernel crash with no mitigation possible at runtime. The VC:L rating reflects that MSR reads yield security-sensitive kernel addresses rather than user data directly. No EPSS data was supplied; no CISA KEV listing exists, indicating no confirmed in-the-wild exploitation. However, a public proof-of-concept is available on GitHub (floppywiggler/directio64-disclosure), lowering the exploitation bar significantly for any local attacker. The real-world risk is elevated for environments where these benchmarking or forensics tools are installed on shared or multi-user Windows systems, since a standard user account is sufficient to trigger an instant kernel crash, making this a reliable local DoS/sabotage primitive. The MSR read path is a meaningful KASLR bypass for exploit chain development on affected machines, though chaining to full privilege escalation would require an additional vulnerability. Risk is bounded by the requirement for interactive or shell-level local access. |
| Exploit ScenarioDerived | A standard Windows user account on a machine with PassMark PerformanceTest installed opens a handle to the DirectIo64.sys device, then calls the write IOCTL targeting MSR index 0xC0000082 (IA32_LSTAR) with a zero payload. On the next system call executed by any process on the system, the CPU dereferences the null entry point, causing an immediate and unrecoverable kernel panic (BSOD), crashing all running processes and causing data loss. A public proof-of-concept on GitHub provides ready-made IOCTL call templates, requiring no kernel development expertise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 04, 2026
Privilege escalation and kernel DoS in PassMark's shared DirectIo64.sys kernel driver affect PerformanceTest (before 11.1 build 1012), BurnInTest (before 11.1 build 1000), and OSForensics (before 11.1 build 1016), allowing a local low-privileged attacker to read arbitrary Model-Specific Registers or write zero to any MSR via IOCTLs with an insufficient blocklist. Writing zero to the system call handler MSR (e.g., IA32_LSTAR) causes an immediate unrecoverable kernel panic on the next system call, while reading security-sensitive MSRs (such as those storing kernel base addresses) enables KASLR bypass to support privilege escalation chains. A public proof-of-concept is available via GitHub, and vendor patches have been released; no KEV listing at time of analysis.
RemediationAI
Vendor-released patches are available: upgrade PerformanceTest to 11.1 build 1012 or later, BurnInTest to 11.1 build 1000 or later, and OSForensics to 11.1 build 1016 or later using the respective vendor history pages. The patches are expected to enforce a proper MSR allowlist or blocklist within DirectIo64.sys, restricting accessible MSR indices to only those required for legitimate benchmarking. If immediate patching is not possible, administrators can use Windows Driver Signature Enforcement and Device Guard/HVCI policies to block unsigned or allowlisted drivers, though this may break product functionality. Alternatively, restricting access to the affected products' installation directories and the driver's device object using Windows ACLs or AppLocker can prevent low-privileged users from opening the IOCTL handle. On shared or multi-user systems, uninstalling the affected products until patching is feasible is the safest compensating control, as the DoS primitive requires no elevated privilege to trigger a system crash.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
DirectIo64.sys is a Windows kernel driver (ring-0) distributed with three PassMark products that exposes DeviceIoControl interfaces for direct hardware access. Model-Specific Registers are per-CPU control registers accessible only at CPL-0 (kernel mode) via RDMSR/WRMSR instructions. CWE-782 (Exposed IOCTL with Insufficient Access Control) describes the root cause: the driver implements a blocklist to restrict which MSR indices are accessible, but the enforcement is insufficient, leaving security-critical MSRs reachable from user space. IA32_LSTAR (MSR index 0xC0000082) stores the kernel system call entry point; zeroing it causes a null-pointer dereference on the next SYSCALL instruction, crashing the system. MSRs such as IA32_GS_BASE can reveal kernel structure base addresses, enabling KASLR defeat. Affected CPE strings cover all versions of cpe:2.3:a:passmark_software:performancetest:*:*, cpe:2.3:a:passmark_software:burnintest:*:*, and cpe:2.3:a:passmark_software:osforensics:*:* below the fixed builds.
Know when Performancetest gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
Local access with low privilege suffices; scope change (S:C) applies because writing to a CPU MSR crashes the entire OS kernel, and C:L captures MSR-read KASLR bypass.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
PassMark PerformanceTest before 11.1 build 1012, BurnInTest before 11.1 build 1000, and OSForensics before 11.1 build 1016 contain a privilege escalation and denial-of-service vulnerability in DirectIo64.sys that allows local attackers to read arbitrary Model-Specific Registers or write zero to any MSR through exposed IOCTLs with insufficient blocklist enforcement. Attackers can exploit the unrestricted write IOCTL to zero out the system call handler MSR, causing an immediate unrecoverable kernel crash on the next system call, or read security-sensitive MSRs used to locate kernel data structures.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Performancetest
View allAn issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest through 10. Rat
An issue was discovered in PassMark BurnInTest through 9.1, OSForensics through 7.1, and PerformanceTest through 10. Rat
Arbitrary physical memory write via a hard-coded cryptographic key in the shared Windows kernel driver DirectIo64.sys af
Full physical memory disclosure in PassMark's shared kernel driver DirectIo64.sys affects PerformanceTest (before 11.1 b
Privilege escalation in PassMark's shared DirectIo64.sys kernel driver, bundled with PerformanceTest (before 11.1 build
Unprivileged local users can issue privileged hardware IOCTLs through PassMark's DirectIo64.sys kernel driver across thr
Physical memory disclosure and arbitrary SYSTEM-context file write in PassMark PerformanceTest (before 11.1 build 1012),
An issue was discovered in PassMark BurnInTest v9.1 Build 1008, OSForensics v7.1 Build 1012, and PerformanceTest v10.0 B
Local privilege escalation to kernel in PassMark PerformanceTest, BurnInTest, and OSForensics allows a low-privileged lo
Privilege escalation through the DirectIo64.sys kernel driver affects three PassMark products - PerformanceTest before b
EUVD-2026-71686
GHSA-m6jq-8p5j-c6vp
NVD
CVE.org
EPSS
Exploit-DB