# CVE-2025-15037: Information disclosure in ASUS Business System Control Interface

> Unprivileged local users can access sensitive hardware resources and kernel information via crafted IOCTL requests in the ASUS Business System Control Interface driver.

- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-jv98-ppxj-hj8j

## What is CVE-2025-15037?

CVE-2025-15037 is a medium-severity vulnerability in ASUS Business System Control Interface, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-15037?


## How do I fix CVE-2025-15037?

No fix has been published for CVE-2025-15037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15037 being exploited?

There is no known exploitation of CVE-2025-15037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15037 and fix it if it is affected.

What it is: CVE-2025-15037 is a medium-severity vulnerability in ASUS Business System Control Interface, published on 12 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15037 in the wild and no public exploit code.

Affected product: ASUS Business System Control Interface. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15037/ (Markdown: https://insights.sbomify.com/CVE-2025-15037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15037
- OSV: https://osv.dev/vulnerability/CVE-2025-15037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15037/
Summaries are generated and may contain mistakes; the official description above is the record.