{"api_version":"1","generated_at":"2026-10-22T01:49:01+00:00","cve":"CVE-2026-98845","urls":{"html":"https://cve.report/CVE-2026-98845","api":"https://cve.report/api/cve/CVE-2026-98845.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98845","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98845"},"summary":{"title":"tpm: Disable TPM on null key name mismatch","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Disable TPM on null key name mismatch\n\nThe null key name check exists to protect against TPM reset attacks, so\na mismatch should stop the device from serving further requests.\nCurrently it does not disable the chip when it finds a mismatch.\n\nThe mismatch is logged:\n\n    tpm tpm0: null key integrity check failed\n\nbut the chip keeps serving commands:\n\n    / # tpm2_getcap -c properties-fixed\n    TPM_PT_FAMILY_INDICATOR:\n      as UINT32:                0x08322e3000\n      as string:                \"2.0\"\n    ...\n\ntpm2_load_null() where the null key name check is run sets the chip as\ndisabled only if the rc is non zero. When the mismatch is seen, rc is\nzero at that point and it returns success. The other issue is that the\ncaller expects the null key handle to be populated when the function\nreturns 0 which it does here without writing the handle and proceeds\nassuming the null key handle is valid.\n\nDuring the test, I noticed that tpm2_start_auth_session() uses the\nuninitialized stack value as the key handle since tpm2_load_null()\nreturns 0 despite the integrity failure and proceeds with\nTPM2_CC_START_AUTH_SESS with this value as salt key handle.\n\nSet rc to -ENODEV on the mismatch. The error path then disables the chip\nand returns the correct code to the caller.\n\nTested in QEMU with swtpm and CONFIG_TCG_TPM2_HMAC=y by making\nTPM2_CC_CONTEXT_LOAD fail with TPM2_RC_INTEGRITY and changing the name\nof the re-created null key. The chip is now disabled on the mismatch.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-18 16:17:38","updated_at":"2026-10-19 10:19:48"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a03d0c64cd827a622578623a78defd66b6593b82","name":"https://git.kernel.org/stable/c/a03d0c64cd827a622578623a78defd66b6593b82","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f6599d8830fe7ddab7334cc17846fd9ac9a7fa50","name":"https://git.kernel.org/stable/c/f6599d8830fe7ddab7334cc17846fd9ac9a7fa50","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/015fb29a748342a186f37b602ac70017098c8251","name":"https://git.kernel.org/stable/c/015fb29a748342a186f37b602ac70017098c8251","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa","name":"https://git.kernel.org/stable/c/96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98845","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98845","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cc7d8594342a25693d40fe96f97e5c6c29ee609c a03d0c64cd827a622578623a78defd66b6593b82 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cc7d8594342a25693d40fe96f97e5c6c29ee609c 96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cc7d8594342a25693d40fe96f97e5c6c29ee609c f6599d8830fe7ddab7334cc17846fd9ac9a7fa50 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cc7d8594342a25693d40fe96f97e5c6c29ee609c 015fb29a748342a186f37b602ac70017098c8251 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 294984ce51c19c2af3d0d71e1c8bd589bc86b8e2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 386c7cc6c06d64cbf36d15c5e2319814765e107c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.11.7 6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.11.10 6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.113 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.56 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.10 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/char/tpm/tpm2-sessions.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a03d0c64cd827a622578623a78defd66b6593b82","status":"affected","version":"cc7d8594342a25693d40fe96f97e5c6c29ee609c","versionType":"git"},{"lessThan":"96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa","status":"affected","version":"cc7d8594342a25693d40fe96f97e5c6c29ee609c","versionType":"git"},{"lessThan":"f6599d8830fe7ddab7334cc17846fd9ac9a7fa50","status":"affected","version":"cc7d8594342a25693d40fe96f97e5c6c29ee609c","versionType":"git"},{"lessThan":"015fb29a748342a186f37b602ac70017098c8251","status":"affected","version":"cc7d8594342a25693d40fe96f97e5c6c29ee609c","versionType":"git"},{"status":"affected","version":"294984ce51c19c2af3d0d71e1c8bd589bc86b8e2","versionType":"git"},{"status":"affected","version":"386c7cc6c06d64cbf36d15c5e2319814765e107c","versionType":"git"},{"lessThan":"6.12","status":"affected","version":"6.11.7","versionType":"semver"},{"lessThan":"6.12","status":"affected","version":"6.11.10","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/char/tpm/tpm2-sessions.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.12"},{"lessThan":"6.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.113","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.56","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.10","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.113","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.56","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.10","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Disable TPM on null key name mismatch\n\nThe null key name check exists to protect against TPM reset attacks, so\na mismatch should stop the device from serving further requests.\nCurrently it does not disable the chip when it finds a mismatch.\n\nThe mismatch is logged:\n\n    tpm tpm0: null key integrity check failed\n\nbut the chip keeps serving commands:\n\n    / # tpm2_getcap -c properties-fixed\n    TPM_PT_FAMILY_INDICATOR:\n      as UINT32:                0x08322e3000\n      as string:                \"2.0\"\n    ...\n\ntpm2_load_null() where the null key name check is run sets the chip as\ndisabled only if the rc is non zero. When the mismatch is seen, rc is\nzero at that point and it returns success. The other issue is that the\ncaller expects the null key handle to be populated when the function\nreturns 0 which it does here without writing the handle and proceeds\nassuming the null key handle is valid.\n\nDuring the test, I noticed that tpm2_start_auth_session() uses the\nuninitialized stack value as the key handle since tpm2_load_null()\nreturns 0 despite the integrity failure and proceeds with\nTPM2_CC_START_AUTH_SESS with this value as salt key handle.\n\nSet rc to -ENODEV on the mismatch. The error path then disables the chip\nand returns the correct code to the caller.\n\nTested in QEMU with swtpm and CONFIG_TCG_TPM2_HMAC=y by making\nTPM2_CC_CONTEXT_LOAD fail with TPM2_RC_INTEGRITY and changing the name\nof the re-created null key. The chip is now disabled on the mismatch."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:26:37.375Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a03d0c64cd827a622578623a78defd66b6593b82"},{"url":"https://git.kernel.org/stable/c/96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa"},{"url":"https://git.kernel.org/stable/c/f6599d8830fe7ddab7334cc17846fd9ac9a7fa50"},{"url":"https://git.kernel.org/stable/c/015fb29a748342a186f37b602ac70017098c8251"}],"title":"tpm: Disable TPM on null key name mismatch","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98845","datePublished":"2026-10-18T15:50:27.596Z","dateReserved":"2026-09-25T10:25:14.373Z","dateUpdated":"2026-10-19T09:26:37.375Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-18 16:17:38","lastModifiedDate":"2026-10-19 10:19:48","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98845","Ordinal":"1","Title":"tpm: Disable TPM on null key name mismatch","CVE":"CVE-2026-98845","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98845","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Disable TPM on null key name mismatch\n\nThe null key name check exists to protect against TPM reset attacks, so\na mismatch should stop the device from serving further requests.\nCurrently it does not disable the chip when it finds a mismatch.\n\nThe mismatch is logged:\n\n    tpm tpm0: null key integrity check failed\n\nbut the chip keeps serving commands:\n\n    / # tpm2_getcap -c properties-fixed\n    TPM_PT_FAMILY_INDICATOR:\n      as UINT32:                0x08322e3000\n      as string:                \"2.0\"\n    ...\n\ntpm2_load_null() where the null key name check is run sets the chip as\ndisabled only if the rc is non zero. When the mismatch is seen, rc is\nzero at that point and it returns success. The other issue is that the\ncaller expects the null key handle to be populated when the function\nreturns 0 which it does here without writing the handle and proceeds\nassuming the null key handle is valid.\n\nDuring the test, I noticed that tpm2_start_auth_session() uses the\nuninitialized stack value as the key handle since tpm2_load_null()\nreturns 0 despite the integrity failure and proceeds with\nTPM2_CC_START_AUTH_SESS with this value as salt key handle.\n\nSet rc to -ENODEV on the mismatch. The error path then disables the chip\nand returns the correct code to the caller.\n\nTested in QEMU with swtpm and CONFIG_TCG_TPM2_HMAC=y by making\nTPM2_CC_CONTEXT_LOAD fail with TPM2_RC_INTEGRITY and changing the name\nof the re-created null key. The chip is now disabled on the mismatch.","Type":"Description","Title":"tpm: Disable TPM on null key name mismatch"}]}}}