dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-15038

MEDIUM · 6.9 CVSS v4.0 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
An Out-of-Bounds Read vulnerability exists in the ASUS Business System Control Interface driver. This vulnerability can be triggered by an unprivileged local user sending a specially crafted IOCTL  request, potentially leading to a disclosure of kernel information or a system crash. Refer to the "Security Update for ASUS  Business System Control Interface" 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

An out-of-bounds read vulnerability exists in the ASUS Business System Control Interface driver. An unprivileged local user can trigger this by sending a specially crafted IOCTL request, potentially exposing kernel memory contents or causing a system crash.

MitigationApply the vendor-supplied security update for the ASUS Business System Control Interface driver from the ASUS Security Advisory.

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:H/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. Identify if ASUS Business System Control driver is present
    Search for driver files related to ASUS Business System Control - check %SystemRoot%\System32\drivers folder for files with 'ASUS' and 'Business' or 'ABSI' in the name, or check Program Files for ASUS utility software
    Affected if ASUS Business System Control driver files are found on the system
  2. Retrieve driver file version
    Right-click the driver file, select Properties, then view the Version tab. Alternatively, use PowerShell: Get-ItemProperty 'C:\Windows\System32\drivers\<driverfilename.sys>' | Select-Object VersionInfo
    Affected if The driver version cannot be determined or is earlier than the patched version referenced in ASUS Security Advisory ASA-2025-15038 or similar
  3. Check driver service status
    Open Services (services.msc) and look for a service related to ASUS Business System Control, or run 'sc query' from command prompt to enumerate ASUS-related services
    Affected if An ASUS Business System Control service exists and is running (even if stopped, the vulnerable driver may still be loadable)
  4. Verify driver is loadable
    Check registry under HKLM\SYSTEM\CurrentControlSet\Services for keys matching ASUS Business System Control driver name, or use 'driverquery /v' to list loaded drivers and search for ASUS-related entries
    Affected if The driver appears in the system driver list regardless of current load state

If the ASUS Business System Control driver is installed on the system (files present, service registered, or driver loadable), the environment is potentially affected by this IOCTL 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied security update for the ASUS Business System Control Interface driver from the ASUS Security Advisory.

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