CVE-2026-80118

PassMark PerformanceTest, BurnInTest, and OSForensics Kernel Null Pointer Dereference via DirectIo64.sys IOCTL

HIGH
7.1
CVSS Score
Published: September 4, 2026 at 06:37 PM UTC
Updated: October 1, 2026 at 07:19 PM UTC
3 products affected across 1 vendorPerformanceTestBurnInTestOSForensics

Using PerformanceTest by PassMark Software?

Get instant alerts when new vulnerabilities affect PerformanceTest - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

PassMark PerformanceTest before 11.1 build 1012, BurnInTest before 11.1 build 1000, and OSForensics before 11.1 build 1016 contain an unauthenticated physical memory disclosure in DirectIo64.sys, reachable by unprivileged local users through a single IOCTL with no caller-identity check. The handler writes a crash-dump-format (PAGEDU64) image of all physical memory to a caller-supplied file path in the SYSTEM context, allowing a standard user to create files in locations they cannot otherwise write and to recover memory belonging to processes of other users. The image is preceded by a header that exposes the kernel loaded-module list, active-process list and PFN database pointers, defeating KASLR. The same handler also dereferences the return value of an internal kernel-structure locator without a NULL check; that locator returns NULL on three distinct failure paths, and a kernel crash results on builds where any of those paths is taken.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 11.1 build 1000v < 11.1.1000
Affected range stops below 11.1 build 1000, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.1.1000, so it looks safe — our inference, not a vendor statement
v < 11.1 build 1016v < 11.1.1016
Affected range stops below 11.1 build 1016, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.1.1016, so it looks safe — our inference, not a vendor statement
v < 11.1 build 1012v < 11.1.1012
Affected range stops below 11.1 build 1012, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.1.1012, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHVulnCheck
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-476CWE-73CWE-497

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card