CVE-2026-98845 (GCVE-0-2026-98845)

Vulnerability from cvelistv5 – Published: 2026-10-18 15:50 – Updated: 2026-10-19 09:26
VLAI
Title
tpm: Disable TPM on null key name mismatch
Summary
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.
Severity
No CVSS data available.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: cc7d8594342a25693d40fe96f97e5c6c29ee609c , < a03d0c64cd827a622578623a78defd66b6593b82 (git)
Affected: cc7d8594342a25693d40fe96f97e5c6c29ee609c , < 96c46c75b0d470b4204f9fe1bdb075cd2ebaebfa (git)
Affected: cc7d8594342a25693d40fe96f97e5c6c29ee609c , < f6599d8830fe7ddab7334cc17846fd9ac9a7fa50 (git)
Affected: cc7d8594342a25693d40fe96f97e5c6c29ee609c , < 015fb29a748342a186f37b602ac70017098c8251 (git)
Affected: 294984ce51c19c2af3d0d71e1c8bd589bc86b8e2 (git)
Affected: 386c7cc6c06d64cbf36d15c5e2319814765e107c (git)
Affected: 6.11.7 , < 6.12 (semver)
Affected: 6.11.10 , < 6.12 (semver)
Create a notification for this product.
Linux Linux Affected: 6.12
Unaffected: 0 , < 6.12 (semver)
Unaffected: 6.12.113 , ≤ 6.12.* (semver)
Unaffected: 6.18.56 , ≤ 6.18.* (semver)
Unaffected: 7.2.10 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-98845",
      "date": "2026-11-19",
      "epss": "0.00156",
      "percentile": "0.04885"
    },
    "microsoft_vex": {
      "current_release_date": "2026-11-12T17:55:39.000Z",
      "cve": "CVE-2026-98845",
      "id": "msrc_CVE-2026-98845",
      "initial_release_date": "2026-10-20T22:24:37.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "tpm: Disable TPM on null key name mismatch",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-98845.json",
      "version": "3"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-06T03:16:21+00:00",
      "cve": "CVE-2026-98845",
      "id": "CVE-2026-98845",
      "initial_release_date": "2026-10-18T00:00:00+00:00",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "202",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: tpm: Disable TPM on null key name mismatch",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98845.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.