dbcve.org
CWE-822Weakness · CWE-822

CVE-2026-15029

HIGH · 8.4 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 →
86/100
Remediation priority · High
Zero-click 6 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
Untrusted Pointer Dereference in ASUS System Control Interface v3, ASUS System Control Interface, and ASUS Business Manager allows a local administrator to perform arbitrary physical memory read and write operations via crafted IOCTL requests to the driver, bypassing OS-enforced memory protections. 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

Untrusted pointer dereference in ASUS System Control Interface drivers allows local administrators to send crafted IOCTL requests that perform arbitrary physical memory read/write operations, bypassing OS-enforced memory protections.

MitigationApply vendor patches from ASUS Security Advisory when available; restrict administrative privileges where possible; if the drivers are not required for business functions, consider disabling them.

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:H/VI:H/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 ASUS System Control Interface driver presence
    Open Device Manager, expand 'System devices', and look for drivers with names containing 'ASUS System Control Interface', 'ASUS Splendid', 'ASUS Smart Gesture', or similar ASUS system utilities. Alternatively, run 'driverquery /v | findstr -i asus' from an elevated command prompt.
    Affected if No ASUS System Control Interface drivers are found on the system, the system is not affected by this specific vulnerability.
  2. Check installed driver version
    Right-click the identified ASUS driver in Device Manager, select Properties, go to the Driver tab, and note the Driver Version. Alternatively, use 'wmic path win32_pnpsigneddriver get DeviceName,DriverVersion,DriverDate' filtered for ASUS drivers.
    Affected if The installed driver version falls within or below the affected version range (if ASUS publishes specific version numbers); compare against any ASUS security advisory when available.
  3. Verify driver is currently loaded
    Open Services (services.msc) and check for ASUS-related services such as 'ASUS System Control Service' or 'ASUS Splendid Service', or run 'sc query type= driver' and grep for ASUS entries. Also check 'msinfo32' under 'Loaded System Drivers'.
    Affected if The driver is loaded and running, providing the attack surface for the untrusted pointer dereference flaw.
  4. Confirm administrator-level access exists
    Verify current user privileges by running 'whoami /groups' or 'net session' (requires admin). The vulnerability requires local administrator rights to send the crafted IOCTL requests.
    Affected if The user or account interacting with the system has local administrator privileges, enabling the exploitation path.

The system is affected if ASUS System Control Interface drivers are installed, loaded, and the user has local administrator access, allowing crafted IOCTL requests to perform unauthorized physical memory operations.

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 vendor patches from ASUS Security Advisory when available; restrict administrative privileges where possible; if the drivers are not required for business functions, consider disabling them.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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