dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-9337

MEDIUM · 6.8 CVSS v4.0 Published 2025-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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 has been identified in the AsIO3.sys driver. The vulnerability can be triggered by a specially crafted input, which may lead to a system crash (BSOD). Refer to the 'Security Update for Armoury Crate App' 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 AsIO3.sys kernel-mode driver (used by ASUS Armoury Crate). The flaw can be triggered by specially crafted input, causing the driver to dereference a null pointer, which leads to a system crash (Blue Screen of Death/BSOD). This is a local denial-of-service vulnerability affecting Windows systems with the vulnerable driver installed.

MitigationApply the official ASUS security update for Armoury Crate which includes the patched AsIO3.sys driver. Since this is a kernel-mode driver vulnerability requiring vendor-provided patches, organizations should obtain the update from ASUS and deploy it through their standard patch management processes.

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

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/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. Verify ASUS Armoury Crate installation
    Check for Armoury Crate in Programs and Features or query the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Armoury Crate'
    Affected if Armoury Crate is installed and the AsIO3.sys driver is present
  2. Locate the AsIO3.sys driver file
    Search for AsIO3.sys in typical driver locations such as C:\Windows\System32\drivers\ or within the Armoury Crate installation directory (commonly under C:\Program Files\ASUS\Armoury Crate\)
    Affected if The file AsIO3.sys exists on the system
  3. Retrieve driver file version
    Right-click the AsIO3.sys file, select Properties, then view the Details tab for File Version and Product Version; alternatively use PowerShell: (Get-Item 'C:\Windows\System32\drivers\AsIO3.sys').VersionInfo
    Affected if Driver version is earlier than the patched version released by ASUS (if known) or version cannot be determined
  4. Check if driver is loaded
    Open Command Prompt as Administrator and run: sc query AsIO3 or check Device Manager for hidden devices showing the ASUS AsIO3 driver
    Affected if The AsIO3 driver shows as RUNNING or LOADED in sc query output
  5. Check driver signing status
    Open Command Prompt as Administrator and run: signtool verify /v /pa C:\Windows\System32\drivers\AsIO3.sys
    Affected if Driver is present but fails signature verification or shows as unsigned

If Armoury Crate is installed with the AsIO3.sys driver present and the driver version predates the ASUS security patch, the system is vulnerable to CVE-2025-9337.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the official ASUS security update for Armoury Crate which includes the patched AsIO3.sys driver. Since this is a kernel-mode driver vulnerability requiring vendor-provided patches, organizations should obtain the update from ASUS and deploy it through their standard patch management processes.

Recommended fix Moderate confidence
  1. Navigate to the official ASUS Security Advisory at www.asus.com and locate the 'Security Update for Armoury Crate App' section
  2. Identify the security update addressing CVE-2025-9337 (AsIO3.sys null pointer dereference)
  3. Download and install the recommended Armoury Crate update from ASUS
  4. Reboot the system to ensure the driver update is fully applied
  5. Verify the AsIO3.sys driver version matches the patched version referenced in the advisory

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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