Root persistence via TPM NV_Read out-of-bounds write
Published Apr 15, 2025 · Updated May 8, 2025
Out-of-bounds write in ChromeOS 15753.50.0 on Cr50 boards allows local users with root access to gain persistent boot control. The TPM2 Reference Library's NV_Read handling writes beyond a memory boundary during the challenge-response process. Root privileges and a Cr50-based device are required; successful exploitation bypasses operating-system verification and establishes persistence.
Summary
What happened
Out-of-bounds write in ChromeOS 15753.50.0 on Cr50 boards allows local users with root access to gain persistent boot control. The TPM2 Reference Library's NV_Read handling writes beyond a memory boundary during the challenge-response process. Root privileges and a Cr50-based device are required; successful exploitation bypasses operating-system verification and establishes persistence.
The record
- CVE
- CVE-2025-1122
- Published
- Apr 15, 2025
- Updated
- May 8, 2025
- Vendor
- Product
- ChromeOS
- Classifications
- CWE-787, T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 15, 2025CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15753.50.0 <15753.50.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo