# CVE-2025-2027: Use after free in ASCI

> A double free vulnerability in ASUS System Analysis allows local attackers to crash the service or potentially execute code via crafted RPC requests.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2025
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-q92g-r34h-wrx3

## What is CVE-2025-2027?

CVE-2025-2027 is a medium-severity use after free vulnerability in ASUS ASCI, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A double free vulnerability has been identified in the ASUS System Analysis service. This vulnerability can be triggered by sending specially crafted local RPC requests, leading to the service crash and potentially memory manipulation in some rare circumstances.
Refer to the 'Security Update for MyASUS' section on the ASUS Security Advisory for more information.

Weakness: CWE-415 (Double Free)

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


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

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

## Is CVE-2025-2027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2027 is a medium-severity use after free vulnerability in ASUS ASCI, published on 28 Mar 2025. 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-2027 in the wild and no public exploit code.

Affected product: ASUS ASCI. 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-2027/ (Markdown: https://insights.sbomify.com/CVE-2025-2027/index.md)
```

## Sources

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

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