CVE-2026-98845

tpm: Disable TPM on null key name mismatch

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.

Key facts

Published
18 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.156% likely to be exploited in the next 30 days, higher than 4.854% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • cc7d8594342a25693d40fe96f97e5c6c29ee609c up to but excluding a03d0c64cd827a622578623a78defd66b6593b82 (affected)
  • cc7d8594342a25693d40fe96f97e5c6c29ee609c up to but excluding 96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa (affected)
  • cc7d8594342a25693d40fe96f97e5c6c29ee609c up to but excluding f6599d8830fe7ddab7334cc17846fd9ac9a7fa50 (affected)
  • cc7d8594342a25693d40fe96f97e5c6c29ee609c up to but excluding 015fb29a748342a186f37b602ac70017098c8251 (affected)
  • 294984ce51c19c2af3d0d71e1c8bd589bc86b8e2 (affected)
  • 386c7cc6c06d64cbf36d15c5e2319814765e107c (affected)
  • 6.11.7 up to but excluding 6.12 (affected)
  • 6.11.10 up to but excluding 6.12 (affected)
LinuxLinux
  • Default status: affected
  • 6.12 (affected)
  • 0 up to but excluding 6.12 (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References