# CVE-2025-1122: Memory corruption in ChromeOS

> An attacker with root access can exploit an out-of-bounds write in the TPM2 library to bypass OS verification and gain persistence on ChromeOS devices.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-j93w-j7jm-5c8h

## What is CVE-2025-1122?

CVE-2025-1122 is a medium-severity memory corruption vulnerability in Google Chrome, published on 15 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out-Of-Bounds Write in TPM2 Reference Library in Google ChromeOS 15753.50.0  stable on Cr50 Boards allows an attacker with root access to gain persistence and 
Bypass operating system verification via exploiting the NV_Read functionality during the Challenge-Response process.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Google Chrome.

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

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

## Is CVE-2025-1122 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1122 exists.

Public exploit code:

- RMASmoke main repo. CVE-2025-1122 (github_poc): https://github.com/FWNavy/RMASmoke
- the files/docs for various exploits, such as (LTBEEF, Sh1mmer, CryptoSmite, RMASmoke, aka: CVE-2025-1122, etc.) (github_poc): https://github.com/jenson8161/exploit-docs
- RMASmoke main repo. CVE-2025-1122, (But better) (github_poc): https://github.com/jenson8161/RMASmoke-v2

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1122 is a medium-severity memory corruption vulnerability in Google Chrome, published on 15 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1122 exists.

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

## Sources

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

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