Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Out-of-Bounds Read in TCG TPM 2.0 CryptHmacSign

IdentifiersCVE-2025-2884CWE-125· Out-of-bounds Read

CVE-2025-2884 is an out-of-bounds read vulnerability in the Trusted Computing Group (TCG) TPM 2.0 reference implementation, specifically in the CryptHmacSign helper function. The flaw is caused by insufficient validation that the selected signature scheme is compatible with the signature key's algorithm. When a malformed or incompatible signing request is processed, the TPM implementation can read memory outside the intended bounds. The issue is documented in TCG TPM 2.0 Errata Revision 1.83 and advisory TCGVRT0009. Affected implementations include TPM 2.0 reference-library-derived code prior to the corrected errata, and downstream vendor implementations may inherit the flaw depending on how closely they track the reference implementation.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause the TPM to perform out-of-bounds memory reads, which may disclose sensitive data resident in TPM memory and may also trigger denial of service conditions that render the TPM unstable or inoperable. Available advisory material indicates the practical impact depends on the vendor implementation, but information disclosure and TPM service disruption are the primary consequences.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the TPM command interface to trusted, authorized local users and processes only, minimize exposure of systems that permit untrusted local interaction with TPM functions, and follow vendor hardening guidance. In industrial deployments, isolate affected devices within protected networks, prevent unnecessary remote access, and apply compensating controls around systems exposing TPM-backed functionality until firmware or software updates can be installed.

Remediation

Patch, then assume compromise.

Apply vendor-provided TPM firmware or software updates that incorporate the TCG TPM 2.0 Errata Revision 1.83 fix or equivalent corrections. For libtpms, upgrade to version 0.10.1 or later. CERT/CC advisory material also lists fixed Infineon firmware versions including SLB 9672/9673 FW xx.24, SLB 9670 FW 7.86, SLM/SLI 9670 FW13.16, and SLB 9665 FW 5.66. For affected OEM platforms such as Siemens systems, update to the latest vendor-released fixed product versions where available.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Infineon TechnologiesOptigatm Tpm Slb 9672 / 9673hardware
Infineon TechnologiesSlb 9665hardware
Infineon TechnologiesSlb 9670 Tpm2.0hardware
Infineon TechnologiesSlm/Sli 9670hardware
Trusted Computing GroupTpm 2.0 Reference Implementationhardware
Trusted Computing GroupTpm 2.0 Reference Libraryhardware
Trusted Computing GroupTpm2.0 Reference Implementationapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.