Which versions of ASUS System Control Interface are affected by CVE-2026-15029?

ASUS System Control Interface and Business Manager drivers (v3 and legacy) contain a memory protection bypass that allows local administrators to escalate privileges to kernel level and bypass…

How to fix or mitigate CVE-2026-15029?

Within 24 hours, inventory all systems running ASUS System Control Interface v3/legacy and ASUS Business Manager drivers. Within 7 days, implement driver signature enforcement, restrict IOCTL access to the ASUS driver, and evaluate removing the driver if non-critical. Within 30 days, establish continuous monitoring of ASUS security advisories and deploy patches immediately upon vendor release; verify remediation across all affected systems.

ASUS System Control Interface CVE-2026-15029

Q: What is the CVSS score of CVE-2026-15029?

CVE-2026-15029 has a CVSS 4.0 base score of 8.4 (High). CVSS vector: 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. EPSS exploitation probability: 0.1%.

EUVD-2026-44589 HIGH

Untrusted Pointer Dereference (CWE-822)

2026-07-15 ASUS

GHSA-cvqr-f3j3-pp87

Authentication Bypass Business Manager System Control Interface System Control Interface V3 Asus

8.4

CVSS 4.0 · Vendor: ASUS

Severity by source

Vendor (ASUS) PRIMARY

8.4 HIGH

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

vuln.today AI

6.7 MEDIUM

Local admin must open the driver and send IOCTLs, so AV:L and PR:H with low complexity; physical memory read/write yields full C/I/A impact within an unchanged kernel scope.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ASUS).

CVSS VectorVendor: ASUS

Attack Vector

Local

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 15, 2026 - 02:31 vuln.today

CVE Published

Jul 15, 2026 - 02:01 cve.org

HIGH 8.4

DescriptionCVE.org

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.

AnalysisAI

Arbitrary physical memory read/write in the ASUS System Control Interface (v3 and legacy) and ASUS Business Manager driver allows a local administrator to issue crafted IOCTL requests that bypass OS-enforced memory protections, per an ASUS-published advisory. The flaw (CWE-822, Untrusted Pointer Dereference) turns the signed ASUS driver into a read/write primitive over physical memory, enabling privilege escalation from admin to kernel and potential defense evasion. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; EPSS was not provided.

Technical ContextAI

The affected component is ASUS's user-to-kernel bridge driver shipped with the System Control Interface (SCI) v3 and legacy SCI, and with ASUS Business Manager - utilities preinstalled on ASUS commercial/enterprise notebooks to manage hardware features. The vulnerability class is CWE-822 (Untrusted Pointer Dereference): the driver accepts a pointer or address value from user-controlled IOCTL input and dereferences it without validating that it references a safe, authorized kernel-managed object. Because the handler exposes physical-memory read and write semantics, an attacker-supplied address is mapped and accessed directly, sidestepping virtual-memory isolation, SMEP/SMAP, and other OS-enforced protections. This is the classic 'signed vulnerable driver' (BYOVD-adjacent) pattern where a legitimate, code-signed driver provides an unauthenticated memory primitive to any process able to open the device handle.

RemediationAI

Apply the ASUS-provided update referenced in the 'Security Update for ASUS System Control Interface' section of the ASUS Security Advisory (https://www.asus.com/security-advisory); a fixed version is indicated by the vendor advisory but no exact patched version number is present in the provided data, so confirm the target build directly from that advisory (Patch available per vendor advisory). Update ASUS System Control Interface v3, the legacy System Control Interface, and ASUS Business Manager to the versions ASUS designates as fixed via ASUS DriverHub or Windows Update. Where immediate patching is not possible, compensating controls include uninstalling or disabling the ASUS System Control Interface / Business Manager components if the hardware-management features are unused (trade-off: loss of ASUS function-key, sensor, and manageability features), and enforcing Microsoft's vulnerable/blocklisted driver protections (WDAC / HVCI / Microsoft recommended driver block rules) to prevent loading the vulnerable driver version (trade-off: may break the utility until updated). Since exploitation requires local administrator rights, tightening local admin membership and monitoring for unexpected device-handle opens and raw physical-memory IOCTLs to the driver reduces exposure.