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

CVE-2025-1533

HIGH · 8.2 CVSS v4.0 Published 2025-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
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 · high confidence

A stack buffer overflow vulnerability exists in the AsIO3.sys kernel-mode driver, which is part of ASUS Armoury Crate software. The vulnerability can be triggered through input manipulation, allowing an attacker to overflow a stack-based buffer. This can result in a Blue Screen of Death (BSOD) crash or potentially enable arbitrary code execution with kernel-level privileges.

MitigationApply the security update for Armoury Crate provided by ASUS through their official security advisory. If the update is not immediately available, consider disabling or removing the Armoury Crate service until the patch can be deployed.

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:L/VI:L/VA:H/SC:N/SI:N/SA:H/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 if ASUS Armoury Crate is installed
    Check for Armoury Crate in Programs and Features (appwiz.cpl), or look for the installation folder typically at C:\Program Files\ASUS\Armoury Crate or C:\Program Files (x86)\ASUS\Armoury Crate
    Affected if Armoury Crate is present on the system
  2. Locate the AsIO3.sys driver file
    Search for AsIO3.sys on the system using File Explorer search or command: dir /s C:\AsIO3.sys. The driver is typically located in the Armoury Crate installation directory under a driver or system subfolder
    Affected if AsIO3.sys file exists on the system
  3. Check the driver file version
    Right-click the AsIO3.sys file, select Properties, then view the Details tab to see the File Version. Alternatively, use PowerShell: (Get-Item 'C:\path\to\AsIO3.sys').VersionInfo
    Affected if The file version exists and can be compared to any patched version ASUS releases
  4. Determine if the driver is loaded
    Open Command Prompt as Administrator and run: sc query AsIO3 or check Device Manager for hidden/system devices. Also run: driverquery /v | findstr AsIO3
    Affected if The AsIO3 driver service exists and shows a Running state or the driver is listed as loaded in memory

A system is affected if ASUS Armoury Crate is installed with the AsIO3.sys driver present and loaded, regardless of version, until ASUS releases a specific security patch for this vulnerability.

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 security update for Armoury Crate provided by ASUS through their official security advisory. If the update is not immediately available, consider disabling or removing the Armoury Crate service until the patch can be deployed.

Recommended fix Moderate confidence

Latest Armoury Crate release (contact ASUS support or check the security advisory for the exact version number)

  1. Navigate to the official ASUS Security Advisory page for 'Security Update for Armoury Crate App' at www.asus.com
  2. Identify the specific security update addressing CVE-2025-1533
  3. Download the latest version of Armoury Crate from the official ASUS support page
  4. Uninstall the current version of Armoury Crate from your system
  5. Install the updated Armoury Crate version that includes the fix for the AsIO3.sys driver vulnerability
  6. Restart your computer to ensure the new driver loads correctly
  7. Verify the driver version by checking the AsIO3.sys file properties or using device manager
Caveat ASUS software updates may include feature changes; review the changelog before updating if concerned about functionality changes

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
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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