TPM service interruption via unreleased locality
Published May 27, 2026 · Updated May 27, 2026
Improper cleanup in the Linux Kernel st33zp24 TPM driver interrupts TPM access after an I2C or SPI communication timeout. The st33zp24_send() error path returns when get_burstcount() reports -EBUSY but fails to relinquish the TPM locality acquired earlier, leaving it unavailable for later operations. The condition requires a hardware communication timeout that cannot be invoked or influenced from userspace, so the resulting impact is limited to TPM availability.
Summary
What happened
Improper cleanup in the Linux Kernel st33zp24 TPM driver interrupts TPM access after an I2C or SPI communication timeout. The st33zp24_send() error path returns when get_burstcount() reports -EBUSY but fails to relinquish the TPM locality acquired earlier, leaving it unavailable for later operations. The condition requires a hardware communication timeout that cannot be invoked or influenced from userspace, so the resulting impact is limited to TPM availability.
The record
- CVE
- CVE-2026-45871
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=4.1
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <1256c6dc96d1e687e6e9b63088156ed07411b00c
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <3e91b44c93ad2871f89fc2a98c5e4fe6ca5db3d9
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <4fffb77d35d038f146e6192da583dbe4971d869e
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <7687133509cf66ced120b667fefd21f80bf17993
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <a51cff9be046e13e1c1b2fe45d5c48b582ec9b8c
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <cc09d55f519e15355de343264a22ac6682b8305e
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <e0ce3da82341fcd6194175f1837946b2a894c625
- Affected versionversion=bf38b8710892333cec2d8069644eb36ff435fd6f <ec15eb67fe9df87981b4829b901ec254273ca483
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.
Weakness, pattern, technique
No sourced classifications are available.
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