CVE-2026-98845
Severity unknownNo known exploitationFix availabletpm: Disable TPM on null key name mismatch
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 5% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
In the Linux kernel, the following vulnerability has been resolved: tpm: Disable TPM on null key name mismatch The null key name check exists to protect against TPM reset attacks, so a mismatch should stop the device from serving further requests. Currently it does not disable the chip when it finds a mismatch. The mismatch is logged: tpm tpm0: null key integrity check failed but the chip keeps serving commands: / # tpm2_getcap -c properties-fixed TPM_PT_FAMILY_INDICATOR: as UINT32: 0x08322e3000 as string: "2.0" ... tpm2_load_null() where the null key name check is run sets the chip as disabled only if the rc is non zero. When the mismatch is seen, rc is zero at that point and it returns success. The other issue is that the caller expects the null key handle to be populated when the function returns 0 which it does here without writing the handle and proceeds assuming the null key handle is valid. During the test, I noticed that tpm2_start_auth_session() uses the uninitialized stack value as the key handle since tpm2_load_null() returns 0 despite the integrity failure and proceeds with TPM2_CC_START_AUTH_SESS with this value as salt key handle. Set rc to -ENODEV on the mismatch. The error path then disables the chip and returns the correct code to the caller. Tested in QEMU with swtpm and CONFIG_TCG_TPM2_HMAC=y by making TPM2_CC_CONTEXT_LOAD fail with TPM2_RC_INTEGRITY and changing the name of the re-created null key. The chip is now disabled on the mismatch.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 6.11.10 before 6.12 | 6.12 | CVE Program |
| Linux | Linux | from 6.11.7 before 6.12 | 6.12 | CVE Program |
| Linux | Linux | from cc7d8594342a25693d40fe96f97e5c6c29ee609c before 96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa | 96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa | CVE Program |
| Linux | Linux | from cc7d8594342a25693d40fe96f97e5c6c29ee609c before f6599d8830fe7ddab7334cc17846fd9ac9a7fa50 | f6599d8830fe7ddab7334cc17846fd9ac9a7fa50 | CVE Program |
| Linux | Linux | from cc7d8594342a25693d40fe96f97e5c6c29ee609c before 015fb29a748342a186f37b602ac70017098c8251 | 015fb29a748342a186f37b602ac70017098c8251 | CVE Program |
| Linux | Linux | from cc7d8594342a25693d40fe96f97e5c6c29ee609c before a03d0c64cd827a622578623a78defd66b6593b82 | a03d0c64cd827a622578623a78defd66b6593b82 | CVE Program |
| Linux | Linux | 294984ce51c19c2af3d0d71e1c8bd589bc86b8e2 | Not documented | CVE Program |
| Linux | Linux | 386c7cc6c06d64cbf36d15c5e2319814765e107c | Not documented | CVE Program |
| Linux | Linux | 6.12 | Not documented | CVE Program |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| Linux | Linux (unaffected) | from 6.12.113 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.56 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.2.10 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 6.12 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/015fb29a748342a186f37b602ac70017098c8251 (opens in a new tab)
- https://git.kernel.org/stable/c/96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa (opens in a new tab)
- https://git.kernel.org/stable/c/a03d0c64cd827a622578623a78defd66b6593b82 (opens in a new tab)
- https://git.kernel.org/stable/c/f6599d8830fe7ddab7334cc17846fd9ac9a7fa50 (opens in a new tab)