CVE-2026-46096: tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public()
In the Linux kernel, the following vulnerability has been resolved:
tpm2-sessions: Fix missing tpm_buf_destroy() in tpm2_read_public()
tpm2_read_public() calls tpm_buf_init() but fails to call
tpm_buf_destroy() on two exit paths, leaking a page allocation:
1. When name_size() returns an error (unrecognized hash algorithm),
the function returns directly without destroying the buffer.
2. On the success path, the buffer is never destroyed before
returning.
All other error paths in the function correctly call
tpm_buf_destroy() before returning.
Fix both by adding the missing tpm_buf_destroy() calls.
Security readout for executives and security teams
Plain-English summary
CVE-2026-46096 is a Linux kernel TPM2-session memory leak. A kernel function allocates a buffer and misses cleanup on two return paths, leaking a page allocation. The available sources do not provide CVSS, distribution impact, or evidence of active exploitation.
Executive priority
Treat this as routine-to-moderate kernel maintenance unless your environment depends heavily on TPM2 paths or has unpatched custom kernels. There is no source-backed evidence of active exploitation, but kernel memory leaks can affect availability over time.
Technical view
The issue is in tpm2_read_public(). It calls tpm_buf_init() but fails to call tpm_buf_destroy() on the success path and when name_size() errors on an unrecognized hash algorithm. Stable kernel commits add the missing cleanup calls.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions with the relevant TPM2 code path. The source bundle lists Linux kernel affected entries but does not identify affected distributions, configurations, or remote attack surface.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source reports active exploitation. Based on the description, the plausible impact is resource leakage, but exploitability and practical denial-of-service conditions are not established here.
Researcher notes
The record is precise about the missing tpm_buf_destroy() calls but sparse on impact. Key gaps are CVSS, CWE, triggerability, privilege requirements, and distribution mapping. Avoid assuming exploitability beyond a kernel page-allocation leak without additional vendor analysis.
Mitigation direction
Review vendor kernel advisories for your Linux distribution.
Update to a kernel containing the referenced stable fixes.
Prioritize systems using TPM2 functionality or kernel versions listed as affected.
Track distribution backports rather than relying only on upstream version numbers.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and appliances.
Check whether vendor kernel packages include the referenced upstream fixes.
Confirm TPM2 support or usage on potentially affected systems.
Monitor kernel logs and reliability signals for unusual resource pressure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46096 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:58 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.