# CVE-2026-80118: PassMark PerformanceTest, BurnInTest, and OSForensics Kernel Null Pointer Dereference via DirectIo64.sys IOCTL

> Unprivileged local users can read physical memory, bypass KASLR, write files as SYSTEM, and crash the kernel via a vulnerable driver IOCTL.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-jmfx-96g9-5g4f

## What is CVE-2026-80118?

CVE-2026-80118 is a high-severity vulnerability in PassMark Software BurnInTest, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-73 (External Control of File Name or Path), CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-80118?


## How do I fix CVE-2026-80118?

No fix has been published for CVE-2026-80118 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80118 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80118 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80118 and fix it if it is affected.

What it is: CVE-2026-80118 is a high-severity vulnerability in PassMark Software BurnInTest, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80118 exists.

Affected product: PassMark Software BurnInTest. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80118/ (Markdown: https://insights.sbomify.com/CVE-2026-80118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80118
- OSV: https://osv.dev/vulnerability/CVE-2026-80118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80118/
Summaries are generated and may contain mistakes; the official description above is the record.