CVE-2021-46922: KEYS: trusted: Fix TPM reservation for seal/unseal
In the Linux kernel, the following vulnerability has been resolved:
KEYS: trusted: Fix TPM reservation for seal/unseal
The original patch 8c657a0590de ("KEYS: trusted: Reserve TPM for seal
and unseal operations") was correct on the mailing list:
https://lore.kernel.org/linux-integrity/20210128235621.127925-4-jarkko@kernel.org/
But somehow got rebased so that the tpm_try_get_ops() in
tpm2_seal_trusted() got lost. This causes an imbalanced put of the
TPM ops and causes oopses on TIS based hardware.
This fix puts back the lost tpm_try_get_ops()
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected systems during TPM-backed trusted key operations. It is most relevant where TPM trusted keys are used for sealing or unsealing secrets. The public record does not provide CVSS, a CWE, or evidence of active exploitation.
Executive priority
Treat this as a targeted reliability and availability issue, not a broad emergency based on current evidence. Prioritize patching where TPM-backed trusted keys protect operational secrets or uptime matters.
Technical view
A trusted keys regression lost a TPM reservation call in tpm2_seal_trusted(). Later cleanup could release TPM ops without a matching acquire, causing kernel oopses on TIS-based TPM hardware. Stable kernel fixes restore the missing tpm_try_get_ops() handling.
Likely exposure
Exposure appears limited to Linux systems using TPM trusted keys, especially with TIS-based TPM hardware. The bundle does not provide CPEs, distribution package names, or complete affected version ranges.
Exploitation context
The CVE is not listed as KEV in the bundle. The sources describe kernel oopses from an internal TPM operation imbalance, not confirmed active exploitation or remote attack behavior.
Researcher notes
The public bundle is sparse: no CVSS, CWE, CPEs, exploit evidence, or distro mappings. Analysis should stay anchored to the kernel trusted keys TPM reservation regression and the referenced stable fixes.
Mitigation direction
Apply vendor or distribution kernels containing the referenced stable fixes.
Prioritize systems using TPM trusted keys for sealing or unsealing secrets.
Check Linux distribution advisories for exact fixed package versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-46922 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.