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

CVE-2026-3508

MEDIUM · 6.8 CVSS v4.0 Published 2026-05-08
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 Out-of-bounds Read vulnerability in the IOCTL handler in ASUS System Control Interface allows a local user to cause system crash (BSOD) via a read size that exceeds the buffer size.Refer to the ' Security Update for MyASUS ' 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 · high confidence

An out-of-bounds read vulnerability exists in the IOCTL handler of the ASUS System Control Interface driver. The vulnerability is triggered when a local user submits a read request with a size parameter that exceeds the allocated buffer size, causing the driver to read beyond its bounds and resulting in a Blue Screen of Death (BSOD). This is a kernel-level driver vulnerability affecting Windows systems with ASUS System Control Interface installed.

MitigationApply the official ASUS security update for MyASUS/System Control Interface as soon as it becomes available. Until the patch is applied, consider restricting local user privileges or evaluating whether the service can be safely disabled if not required.

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:N/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. Verify ASUS System Control Interface driver is installed
    Open Services (services.msc) and look for 'ASUS System Control Interface' service, or check Device Manager under System devices for an ASUS driver entry
    Affected if The service or driver entry exists on the system
  2. Identify the driver file version
    Locate the driver file (commonly in C:\Windows\System32\drivers\ or within the MyASUS installation folder), right-click the driver .sys or .dll file, select Properties, and view the Version tab for the File Version
    Affected if The displayed version falls within any vulnerable version range published by ASUS for this CVE
  3. Confirm the vulnerable service is running
    In Services (services.msc), locate the ASUS System Control Interface service and check the Status column; if running, the service is actively processing IOCTL requests
    Affected if The service Status shows 'Running' while the driver version is unpatched
  4. Check for recent ASUS updates
    Open MyASUS or the Windows Store version of MyASUS, navigate to Settings or Support, and check the version or update history to see if a security patch has been applied
    Affected if No security update addressing this CVE has been installed or the version remains unpatched
  5. Review security event logs for BSOD or driver errors
    Open Event Viewer, navigate to Windows Logs\System, and look for Event ID 1001 (Bugcheck) or driver-related errors mentioning ASUS System Control Interface around the time of any crashes
    Affected if Recent BSOD events correlate with the ASUS driver and the driver remains at an unpatched version

The environment is affected if ASUS System Control Interface driver is present with an unpatched version and the service is running, as the IOCTL handler will accept oversized read requests causing the out-of-bounds read condition.

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 official ASUS security update for MyASUS/System Control Interface as soon as it becomes available. Until the patch is applied, consider restricting local user privileges or evaluating whether the service can be safely disabled if not required.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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