dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-15037

MEDIUM · 6.8 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 →
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
An Incorrect Permission Assignment 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 unauthorized access to sensitive hardware resources and kernel information disclosure. Refer to the "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

The ASUS Business System Control Interface driver contains an Incorrect Permission Assignment vulnerability where unprivileged local users can send specially crafted IOCTL (I/O Control) requests to the driver, potentially bypassing access controls and gaining unauthorized access to sensitive hardware resources and kernel memory information.

MitigationApply the vendor patch from ASUS Security Advisory to update the Business System Control Interface driver to a patched version. If no patch is available, disable or remove the vulnerable driver until a fix 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:H/VI:N/VA:N/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. Locate the ASUS Business System Control Interface driver file
    Search for ASUS driver files in system directories. Common locations: C:\Windows\System32\drivers\, C:\Windows\SysWOW64\drivers\, or C:\Program Files\ASUS\. Look for files with 'ASUS' and driver-related names (typically .sys files). Use: Get-ChildItem -Path C:\Windows\System32\drivers\ -Recurse -Filter '*ASUS*' -ErrorAction SilentlyContinue
    Affected if The driver file exists on the system in any driver directory
  2. Verify the driver is currently loaded
    Open Command Prompt as Administrator and run: sc query type= driver state= all | findstr /i "ASUS" or check Device Manager > View > Show hidden devices > Non-Plug and Play Drivers for ASUS entries
    Affected if The driver shows as RUNNING or LOADED in sc query output or Device Manager
  3. Retrieve the driver file version
    Right-click the driver .sys file > Properties > Details tab, or use: wmic datafile where "Name='C:\Path\To\Driver.sys'" get Version
    Affected if File version information is present (indicates the driver is installed)
  4. Check driver file permissions
    Right-click the driver file > Properties > Security tab. Check which users/groups have Read, Write, or Execute permissions. Also run: icacls "C:\Path\To\Driver.sys" to see effective permissions for your user account
    Affected if Unprivileged (non-admin) users have permission to read or write to the driver file, or can send IOCTL requests to it
  5. Test for IOCTL access from unprivileged context
    As a standard (non-admin) user, attempt to interact with the driver using DeviceIoControl API or tools likewinobj to see if access is granted. Check if the driver device object (\\Device\\ASUSBCI or similar) is accessible
    Affected if Unprivileged users can open or send requests to the driver device without being denied

If the ASUS Business System Control Interface driver is present on the system and unprivileged users can access its device object or driver file, the environment is affected by 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.

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

Apply the vendor patch from ASUS Security Advisory to update the Business System Control Interface driver to a patched version. If no patch is available, disable or remove the vulnerable driver until a fix can be deployed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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