Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98845tpm: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected cc7d8594342a25693d40fe96f97e5c6c29ee609c – < a03d0c64cd827a622578623a78defd66b6593b82
    • affected cc7d8594342a25693d40fe96f97e5c6c29ee609c – < 96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa
    • affected cc7d8594342a25693d40fe96f97e5c6c29ee609c – < f6599d8830fe7ddab7334cc17846fd9ac9a7fa50
    • affected cc7d8594342a25693d40fe96f97e5c6c29ee609c – < 015fb29a748342a186f37b602ac70017098c8251
    • affected 294984ce51c19c2af3d0d71e1c8bd589bc86b8e2
    • affected 386c7cc6c06d64cbf36d15c5e2319814765e107c
    • affected 6.11.7 – < 6.12
    • affected 6.11.10 – < 6.12
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98845 badge
[![CVE-2026-98845](https://cveledger.app/badge/CVE-2026-98845.svg)](https://cveledger.app/cve/CVE-2026-98845)

Record last updated .