Loading vulnerability…
An out-of-bounds write vulnerability exists in the TPM2 Reference Library as used in Google ChromeOS 15753.50.0 stable on Cr50 Boards. The vulnerability can be exploited by an attacker with root access, specifically by abusing the NV_Read functionality during the Challenge-Response process. This allows the attacker to write outside the intended memory bounds, potentially corrupting memory and altering the behavior of the TPM firmware.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository, 'RMASmoke', is an exploit toolkit targeting ChromeOS devices with TPM2 chips. Its primary purpose is to disable write-protect by exploiting an out-of-bounds write vulnerability in the TPM2. The repository contains C++ source code (notably src/main.cpp) that implements the core exploit logic, interacting directly with the TPM2 device node (/dev/tpm0) to manipulate NVRAM spaces and trigger the vulnerability. Several shell scripts (build_shim.sh, rmasmoke_shim.sh, factory_install.sh, chromiumos_vm_deploy.sh) automate the process of building, deploying, and executing the exploit in a ChromeOS environment, including mounting partitions and installing the exploit binary. The exploit requires local access to the device, with sufficient privileges to interact with the TPM and modify system partitions. The code is operational and includes all necessary components to build and deploy the exploit, but is not part of a larger exploitation framework. No network endpoints are involved; all actions are performed locally on the target device.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.