TPM service interruption via leaked transient handles
Published Oct 21, 2024 · Updated May 12, 2026
Incomplete cleanup in the Linux TPM command path allows local users to exhaust transient handles after failed TPM commands. tpm_dev_transmit prepares a TPM space before transmission but does not flush that space when transmission fails, leaving transient handles allocated after closure. Exploitation requires local low-privileged TPM access, and repeated failures can interrupt TPM-dependent operations.
Summary
What happened
Incomplete cleanup in the Linux TPM command path allows local users to exhaust transient handles after failed TPM commands. tpm_dev_transmit prepares a TPM space before transmission but does not flush that space when transmission fails, leaving transient handles allocated after closure. Exploitation requires local low-privileged TPM access, and repeated failures can interrupt TPM-dependent operations.
The record
- CVE
- CVE-2024-49851
- Published
- Oct 21, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- CWE-459, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record 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=0 <V3.2
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