# CVE-2025-52347: Privilege escalation in n/a

> Attackers can escalate privileges and access kernel memory via a crafted IOCTL call in PassMark system utilities.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-r85q-xw89-6h26

## What is CVE-2025-52347?

CVE-2025-52347 is a high-severity vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in the component DirectIo64.sys of PassMark BurnInTest v11.0 Build 1011, OSForensics v11.1 Build 1007, and PerformanceTest v11.1 Build 1004 allows attackers to access kernel memory and escalate privileges via a crafted IOCTL 0x8011E044 call.

Weakness: CWE-269 (Improper Privilege Management), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-52347?


## How do I fix CVE-2025-52347?

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

## Is CVE-2025-52347 being exploited?

There is no known exploitation of CVE-2025-52347 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52347 and fix it if it is affected.

What it is: CVE-2025-52347 is a high-severity vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52347 in the wild and no public exploit code.

Affected product: n/a. 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-2025-52347/ (Markdown: https://insights.sbomify.com/CVE-2025-52347/index.md)
```

## Sources

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

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