# CVE-2025-6398: Null dereference in AI Suite

> A null pointer dereference in the ASUS AI Suite 3 driver allows attackers to cause a system crash via crafted input.

- **Severity:** Medium 6.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2025
- **Updated:** 1 Aug 2025
- **Also known as:** GHSA-xxw5-6rch-9wmx

## What is CVE-2025-6398?

CVE-2025-6398 is a medium-severity vulnerability in ASUS AI Suite, published on 1 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2025-6398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6398 is a medium-severity vulnerability in ASUS AI Suite, published on 1 Aug 2025. 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-6398 in the wild and no public exploit code.

Affected product: ASUS AI Suite. 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-6398/ (Markdown: https://insights.sbomify.com/CVE-2025-6398/index.md)
```

## Sources

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

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