Improper key instantiation via overwritten TPM-unseal errors
Published Nov 2, 2026 · Updated Nov 2, 2026
Error handling in Linux 5.13 trusted keys allows local users to instantiate a key despite a failed TPM unseal operation. In trusted_tpm_unseal(), processing continues after unseal failure, and a successful pcrlock() call overwrites the error with success. This requires the TPM trusted-key path, a requested PCR lock, and CAP_SYS_ADMIN; the documented consequence is successful key instantiation, not demonstrated recovery of sealed key material.
Summary
What happened
Error handling in Linux 5.13 trusted keys allows local users to instantiate a key despite a failed TPM unseal operation. In trusted_tpm_unseal(), processing continues after unseal failure, and a successful pcrlock() call overwrites the error with success. This requires the TPM trusted-key path, a requested PCR lock, and CAP_SYS_ADMIN; the documented consequence is successful key instantiation, not demonstrated recovery of sealed key material.
The record
- CVE
- CVE-2026-99221
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 2, 2026CVE publishedPublication date reported by the CVE source.
- Nov 2, 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=5.13
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <234d09bb3b3d84851d4b3246272addc30f3353eb
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <2d92a0f87c338a08367aff05edd1ade86da4ac8d
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <4876f09ce222e140a73aad950882b3605440c935
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <63b19ec2863b2cb5279b746ecd3d6210b1a93945
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <6e359d8cb8580b9874801dea930086effd4d9c62
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <e55d48f21f591a9fe80d26b5fbd1912ea725d9e6
- Affected versionversion=5d0682be318910e028bdf57c90a1695ffc34be37 <ed697a5f667435bbb1cedbe5bd9f300de645047d
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us