dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-9336

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 stack buffer overflow has been identified in the AsIO3.sys driver. This vulnerability can be triggered by input manipulation, may leading to a system crash (BSOD) or other potentially undefined execution. 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 stack buffer overflow vulnerability exists in the AsIO3.sys kernel-mode driver used by ASUS Armoury Crate software. The flaw is triggered through input manipulation, allowing an attacker to overflow a stack-based buffer. This can result in system crashes (Blue Screen of Death) or potentially enable arbitrary code execution with kernel-level privileges.

MitigationApply the security update for Armoury Crate via ASUS's official channels. If immediate patching is not feasible, consider disabling or removing the Armoury Crate application and associated services to reduce the attack surface until the patch can be applied.

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 Armoury Crate installation
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\ASUS for Armoury Crate folder. Alternatively, run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Armoury*"}' in PowerShell.
    Affected if Armoury Crate software is installed on the system.
  2. Locate the AsIO3.sys driver file
    Search for AsIO3.sys on the system using File Explorer or run 'Get-ChildItem -Path C:\ -Recurse -Filter AsIO3.sys -ErrorAction SilentlyContinue' in PowerShell. Common paths include C:\Windows\System32\drivers\ or the Armoury Crate installation directory.
    Affected if The AsIO3.sys file exists on the system.
  3. Check if the driver is currently loaded
    Run 'Get-WmiObject Win32_SystemDriver | Where-Object {$_.Name -like "*AsIO*"}' or check Services (services.msc) for ASUS services related to Armoury Crate. Also run 'driverquery /v | findstr AsIO' in Command Prompt.
    Affected if The AsIO3 driver is listed as a running service or loaded driver.
  4. Inspect driver file version
    Right-click the AsIO3.sys file, select Properties, then go to the Details tab to view File Version. Alternatively, run '(Get-Item "C:\Path\To\AsIO3.sys").VersionInfo' in PowerShell.
    Affected if A version number is displayed (compare to any ASUS-released fixed versions through official channels).
  5. Verify Armoury Crate services are running
    Open Services (services.msc) and look for services named 'Armoury Crate Service', 'ASUS Armoury Crate', or similar. Run 'Get-Service | Where-Object {$_.DisplayName -like "*Armoury*"}' in PowerShell.
    Affected if Any Armoury Crate related services are in a Running state.

The system is affected if Armoury Crate software is installed with the AsIO3.sys driver present and loaded, as the vulnerability resides in this driver and can be triggered when the driver is active.

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 security update for Armoury Crate via ASUS's official channels. If immediate patching is not feasible, consider disabling or removing the Armoury Crate application and associated services to reduce the attack surface until the patch can be applied.

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-9336 — 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-9336 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