dbcve.org
CWE-226Weakness · CWE-226

CVE-2026-13585

HIGH · 8.2 CVSS v4.0 Published 2026-07-15
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 5 weeks old

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
Allocation of Resources Without Limits and Throttling and Sensitive Information in Resource Not Removed Before Reuse in the ASUS System Control Interface driver and ASUS Business Manager allow a local administrator to disclose sensitive information via crafted IOCTL requests, which, in severe cases, may lead to a Denial of Service (DoS) on the system. Refer to the '  Security Update for ASUS 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

This vulnerability in ASUS System Control Interface driver and ASUS Business Manager involves two distinct issues: improper resource allocation limits allowing potential resource exhaustion, and failure to clear sensitive information from memory before reuse. A local administrator can exploit these flaws via crafted IOCTL (I/O Control) requests to disclose sensitive information, potentially leading to system DoS.

MitigationApply the vendor patch from ASUS Security Advisory for System Control Interface. Until patch is available, consider restricting administrative access, monitoring for anomalous IOCTL activity, or disabling non-essential ASUS management services if business requirements permit.

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

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:H/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. Identify ASUS System Control Interface driver presence
    Check for ASUS System Control Interface driver files in system directories (typically under C:\Program Files\ASUS or C:\Windows\System32\drivers) or list installed drivers using 'driverquery /v' and search for ASUS-related driver names
    Affected if ASUS System Control Interface driver is installed on the system
  2. Identify ASUS Business Manager installation
    Check for ASUS Business Manager installation via Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or examine Program Files directory for ASUS Business Manager folder
    Affected if ASUS Business Manager application is installed
  3. Verify ASUS management services are running
    Open Services console (services.msc) and look for ASUS-related services such as 'ASUS System Control Interface Service' or 'ASUS Business Manager' service, or query via 'sc query type= service state= all' and filter for ASUS entries
    Affected if ASUS management services are running and enabled
  4. Check for IOCTL interface exposure
    Examine driver communication endpoints using tools like 'winobj' or 'Sysinternals Suite' to identify if ASUS driver IOCTL handlers are exposed, or review driver device object names under \Device\ and \GLOBAL??\ for ASUS-related entries
    Affected if ASUS driver IOCTL interface is accessible or registered on the system
  5. Monitor for anomalous IOCTL request patterns
    Use kernel-level monitoring tools (such as sysinternals ProcMon with driver filtering) to capture IOCTL requests sent to ASUS driver devices, or review Windows Event Logs for ASUS driver-related errors or warnings
    Affected if Unusual or excessive IOCTL requests to ASUS drivers are observed, or driver event logs show resource allocation failures
  6. Verify memory handling configuration
    Review ASUS driver memory management settings via registry keys under HKLM\SYSTEM\CurrentControlSet\Services\ASUS driver entries if available, or examine crash dumps/Event Viewer for memory corruption indicators related to ASUS services
    Affected if Memory handling misconfigurations exist or memory-related errors involving ASUS drivers are logged

A system is affected if it has ASUS System Control Interface driver or ASUS Business Manager installed with their services running, enabling the vulnerable IOCTL interface for potential resource exhaustion or sensitive information disclosure.

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 for System Control Interface. Until patch is available, consider restricting administrative access, monitoring for anomalous IOCTL activity, or disabling non-essential ASUS management services if business requirements permit.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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