CVE-2026-46283

Cryptographic material persistence via unsanitized TPM teardown

Published Jun 8, 2026 · Updated Jun 8, 2026

Sensitive-data persistence in the Linux Kernel TPM driver leaves cryptographic session material in freed slab memory after TPM device teardown. The tpm_dev_release() path passes chip->auth to kfree() without clearing the tpm2_auth structure, preserving HMAC keys, nonces, and passphrase data until reuse. The published record does not identify how attackers can trigger teardown or reclaim and read that slab memory, so practical exposure is unspecified.

CVSS severity5.5
Medium
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive-data persistence in the Linux Kernel TPM driver leaves cryptographic session material in freed slab memory after TPM device teardown. The tpm_dev_release() path passes chip->auth to kfree() without clearing the tpm2_auth structure, preserving HMAC keys, nonces, and passphrase data until reuse. The published record does not identify how attackers can trigger teardown or reclaim and read that slab memory, so practical exposure is unspecified.

The record

CVE
CVE-2026-46283
Published
Jun 8, 2026
Updated
Jun 8, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.10
  2. Affected versionversion=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <53e6d2d834df40960b655b353e7a8ff4d927e1c7
  3. Affected versionversion=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <84ced03172da544c9f8c0862faad48104f519352
  4. Affected versionversion=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <c424d2664f08c77f08b4580b5f0cbaabf7c229b2
  5. Affected versionversion=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <dd3ac52ea7a001406c7dbc663aae4b9f89da679a

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=6.10; version=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <53e6d2d834df40960b655b353e7a8ff4d927e1c7; version=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <84ced03172da544c9f8c0862faad48104f519352; version=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <c424d2664f08c77f08b4580b5f0cbaabf7c229b2; version=699e3efd6c645c741ea4d6d58282c56b6d108cf7 <dd3ac52ea7a001406c7dbc663aae4b9f89da679a

Published CVSS scores

5.5NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo