CVE-2026-99221
keys/trusted_keys: return immediately after TPM unseal failure
What happened?
In the Linux kernel, the following vulnerability has been resolved:
keys/trusted_keys: return immediately after TPM unseal failure
trusted_tpm_unseal() proceeds to pcrlock() when the TPM unseal operation fails. If pcrlock() succeeds, its return value overwrites the unseal error, causing key instantiation to succeed.
Return immediately when unseal fails to preserve the original error.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < 4876f09ce222e140a73aad950882b3605440c935; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < 2d92a0f87c338a08367aff05edd1ade86da4ac8d; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < 234d09bb3b3d84851d4b3246272addc30f3353eb; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < 6e359d8cb8580b9874801dea930086effd4d9c62; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < e55d48f21f591a9fe80d26b5fbd1912ea725d9e6; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < 63b19ec2863b2cb5279b746ecd3d6210b1a93945; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < ed697a5f667435bbb1cedbe5bd9f300de645047d; affected: 5d0682be318910e028bdf57c90a1695ffc34be37 to < f92d0ccb05bf9089072cb067dda0dffd5394c4ef | See vendor advisory |
| LinuxLinux | affected: 5.13; unaffected: 0 to < 5.13; unaffected: 5.15.224 to ≤ 5.15.*; unaffected: 6.1.191 to ≤ 6.1.*; unaffected: 6.6.161 to ≤ 6.6.*; unaffected: 6.12.115 to ≤ 6.12.*; unaffected: 6.18.60 to ≤ 6.18.*; unaffected: 7.2.14 to ≤ 7.2.*; unaffected: 7.3.1 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99221
- https://git.kernel.org/stable/c/4876f09ce222e140a73aad950882b3605440c935
- https://git.kernel.org/stable/c/2d92a0f87c338a08367aff05edd1ade86da4ac8d
- https://git.kernel.org/stable/c/234d09bb3b3d84851d4b3246272addc30f3353eb
- https://git.kernel.org/stable/c/6e359d8cb8580b9874801dea930086effd4d9c62
- https://git.kernel.org/stable/c/e55d48f21f591a9fe80d26b5fbd1912ea725d9e6
- https://git.kernel.org/stable/c/63b19ec2863b2cb5279b746ecd3d6210b1a93945
- https://git.kernel.org/stable/c/ed697a5f667435bbb1cedbe5bd9f300de645047d
- https://git.kernel.org/stable/c/f92d0ccb05bf9089072cb067dda0dffd5394c4ef