dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-6398

MEDIUM · 6.7 CVSS v4.0 Published 2025-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A null pointer dereference vulnerability exists in the IOMap64.sys driver of ASUS AI Suite 3. The vulnerability can be triggered by a specially crafted input, which may lead to a system crash (BSOD). Refer to the ' Security Update for for AI Suite 3 ' section on the ASUS Security Advisory for more information.

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 · moderate confidence

A null pointer dereference vulnerability exists in the IOMap64.sys kernel-mode driver of ASUS AI Suite 3. The vulnerability can be triggered via specially crafted input to the driver, causing a kernel panic (Blue Screen of Death). This is a local denial-of-service vulnerability in a third-party hardware driver.

MitigationApply the official ASUS security update for AI Suite 3 when available. Until then, consider disabling or removing AI Suite 3 if not required, or restrict access to the driver via endpoint controls.

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
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Check if ASUS AI Suite 3 is installed
    Open Programs and Features (appwiz.cpl) or check for ASUS AI Suite 3 in the list of installed applications. Alternatively, look for the ASUS AI Suite 3 installation directory (commonly in C:\Program Files\ASUS\AI Suite 3 or similar paths).
    Affected if ASUS AI Suite 3 is present on the system
  2. Locate the IOMap64.sys driver file
    Search for the file IOMap64.sys on the system. Common paths include the AI Suite 3 installation directory, C:\Windows\System32\drivers, or the driver store. Use File Explorer search or run: dir /s C:\IOMap64.sys
    Affected if The IOMap64.sys driver file exists on the system
  3. Verify the driver is loaded
    Open an elevated Command Prompt and run: sc query IOMap64 or check Device Manager under System devices for ASUS IOMap64. Also check running drivers with: driverquery /v | findstr IOMap64
    Affected if The IOMap64 driver is currently loaded or running as a service
  4. Compare driver version to affected versions
    Right-click on IOMap64.sys, select Properties, then go to the Details tab to view the File Version. Alternatively, use: powershell (Get-Item 'C:\path\to\IOMap64.sys').VersionInfo
    Affected if The installed driver version falls within any known affected version range for this CVE (if specific versions become known)

The system is affected if the IOMap64.sys driver from ASUS AI Suite 3 is present and loaded, as this is a local denial-of-service vulnerability that triggers via crafted input to the running driver.

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 the official ASUS security update for AI Suite 3 when available. Until then, consider disabling or removing AI Suite 3 if not required, or restrict access to the driver via endpoint controls.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6398 — 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-6398 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