# CVE-2026-94146: BioStar BIOS Update Utility IOCTL BSMEM64_W10.sys sub_110BC write-what-where

> Local attackers can exploit a write-what-where vulnerability in the BIOS Update Utility driver to achieve privilege escalation or code execution.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **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:** 21 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-3wfp-66vf-pgv2

## What is CVE-2026-94146?

CVE-2026-94146 is a critical memory corruption vulnerability in BioStar BIOS Update Utility, published on 21 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in BioStar BIOS Update Utility 1.9.7.3. This issue affects the function sub_110BC of the file BSMEM64_W10.sys of the component IOCTL Handler. The manipulation of the argument PhysicalAddress/Size results in write-what-where condition. Attacking locally is a requirement. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-123 (Write-what-where Condition), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-94146?


## How do I fix CVE-2026-94146?

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

## Is CVE-2026-94146 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94146 and fix it if it is affected.

What it is: CVE-2026-94146 is a critical memory corruption vulnerability in BioStar BIOS Update Utility, published on 21 Sep 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-2026-94146 in the wild and no public exploit code.

Affected product: BioStar BIOS Update Utility. 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-2026-94146/ (Markdown: https://insights.sbomify.com/CVE-2026-94146/index.md)
```

## Sources

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

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