PassMark BurnInTest/OSForensics/PerformanceTest IOCTL DirectIo64.sys path information disclosure

Summaryinfo

A vulnerability classified as problematic has been found in PassMark BurnInTest, OSForensics and PerformanceTest. The impacted element is an unknown function of the file DirectIo64.sys of the component IOCTL Handler. Performing a manipulation of the argument path results in information disclosure. This vulnerability was named CVE-2026-80119. The attack needs to be approached locally. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, was found in PassMark BurnInTest, OSForensics and PerformanceTest (version now known). This affects some unknown processing of the file DirectIo64.sys of the component IOCTL Handler. The manipulation of the argument path with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

PassMark PerformanceTest before 11.1 build 1012, BurnInTest before 11.1 build 1000, and OSForensics before 11.1 build 1016 contain an information disclosure vulnerability in DirectIo64.sys that allows unauthenticated local attackers to dump complete physical memory contents by supplying a caller-controlled file path to an exposed IOCTL. Attackers can issue a single IOCTL call to trigger the driver to iterate all physical memory ranges via MmGetPhysicalMemoryRanges and map each page through ZwMapViewOfSection on the PhysicalMemory section object, writing a full RAM image to an attacker-specified path in the SYSTEM context, bypassing user-mode ACLs and exposing LSASS working set, process memory, and cryptographic material from all running processes.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-80119 since 08/25/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• PassMark

Name

• BurnInTest
• OSForensics
• PerformanceTest

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion