CVE-2026-98845

/// Technical 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 noti

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References