# CVE-2025-2509: Memory corruption in ChromeOS

> A malicious guest VM can trigger an out-of-bounds read in Virglrenderer to escape the sandbox and execute arbitrary code on the host.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 6 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-vv54-m573-67vp

## What is CVE-2025-2509?

CVE-2025-2509 is a high-severity memory corruption vulnerability in Google Chrome Os, published on 6 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-of-Bounds Read in Virglrenderer in ChromeOS  16093.57.0 allows a malicious guest VM to achieve arbitrary address access within the crosvm sandboxed process, potentially leading to 
VM escape via crafted vertex elements data triggering an out-of-bounds read in util_format_description.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Google Chrome Os.

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

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

## Is CVE-2025-2509 being exploited?

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

## Other vulnerabilities in Google Chrome Os

- [CVE-2014-1708](https://insights.sbomify.com/CVE-2014-1708/): Code injection in n/a (critical 10.0)
- [CVE-2013-2833](https://insights.sbomify.com/CVE-2013-2833/): Use after free in n/a (critical 10.0)
- [CVE-2013-0915](https://insights.sbomify.com/CVE-2013-0915/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2864](https://insights.sbomify.com/CVE-2012-2864/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4050](https://insights.sbomify.com/CVE-2012-4050/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2509 is a high-severity memory corruption vulnerability in Google Chrome Os, published on 6 May 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-2509 in the wild and no public exploit code.

Affected product: Google Chrome Os. 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-2509/ (Markdown: https://insights.sbomify.com/CVE-2025-2509/index.md)
```

## Sources

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

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