dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-52347

HIGH · 7.8 CVSS v3.1 Published 2026-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability exists in the DirectIo64.sys kernel-mode driver used by PassMark BurnInTest, OSForensics, and PerformanceTest. The driver fails to properly validate inputs when handling IOCTL code 0x8011E044, allowing an attacker with local access to read/write arbitrary kernel memory and escalate privileges to ring 0.

MitigationApply vendor-supplied patches to the affected PassMark applications. Until patched, restrict local unprivileged access to systems running these applications and monitor for suspicious IOCTL activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if DirectIo64.sys driver is loaded
    Run 'driverquery /v | findstr DirectIo64' or check C:\Windows\System32\drivers\DirectIo64.sys existence
    Affected if The DirectIo64.sys driver file exists on the system or is listed in loaded drivers
  2. Check installed PassMark application versions
    Inspect registry under HKLM\SOFTWARE\PassMark\ for BurnInTest, OSForensics, or PerformanceTest, or check Program Files for the application version
    Affected if Any of these three PassMark applications are installed at a version that falls within the affected range (verify against vendor release notes for CVE-2025-52347)
  3. Verify driver version
    Right-click DirectIo64.sys in C:\Windows\System32\drivers\ and view Properties, or use 'driverquery /v /fo list' to find the driver version
    Affected if The driver version predates the CVE-2025-52347 patch from PassMark
  4. Confirm IOCTL 0x8011E044 handler is accessible
    Use Process Explorer or Process Monitor to verify the driver is actively handling IOCTL requests from user-mode applications
    Affected if The driver is actively registered and handling IOCTL communications with user-mode processes

A system is affected if DirectIo64.sys is loaded and any PassMark application (BurnInTest, OSForensics, PerformanceTest) with an unpatched version is installed, allowing local privilege escalation via the vulnerable IOCTL handler.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches to the affected PassMark applications. Until patched, restrict local unprivileged access to systems running these applications and monitor for suspicious IOCTL activity.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52347 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data