CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size
In the Linux kernel, the following vulnerability has been resolved:
tpm2-sessions: Fix out of range indexing in name_size
'name_size' does not have any range checks, and it just directly indexes
with TPM_ALG_ID, which could lead into memory corruption at worst.
Address the issue by only processing known values and returning -EINVAL for
unrecognized values.
Make also 'tpm_buf_append_name' and 'tpm_buf_fill_hmac_session' fallible so
that errors are detected before causing any spurious TPM traffic.
End also the authorization session on failure in both of the functions, as
the session state would be then by definition corrupted.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux TPM 2.0 session handling can let a local, low-privileged user trigger unsafe kernel memory access. Successful exploitation could compromise system confidentiality, integrity, and availability. The issue is rated CVSS 7.8, but the supplied sources do not establish active exploitation.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on shared or locally accessible systems using TPM-backed security. It is not supported as an emergency internet-wide threat because exploitation requires local access and no active exploitation is documented.
Technical view
The TPM session code used an unchecked TPM_ALG_ID to index name_size data, creating an out-of-range access and possible memory corruption. The fix accepts only known algorithm identifiers, returns -EINVAL otherwise, propagates errors from related TPM buffer functions, and terminates corrupted authorization sessions.
Likely exposure
Exposure is limited to Linux systems running affected kernel code and using relevant TPM 2.0 session paths. The bundle lists affected releases including 6.10, 6.12.66, 6.18.3, and 6.19, but its version metadata is ambiguous. Distribution-specific backports may change actual exposure.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction. KEV is false, and the supplied sources provide no evidence of active exploitation, public proof-of-concept availability, or remote reachability.
Researcher notes
The security boundary is the unchecked algorithm identifier used for name-size indexing. Review distribution patches against the referenced stable commits, including error propagation and session termination changes. The supplied record has unclear version-range encoding and provides no CWE, exploit evidence, or compromise indicators.
Mitigation direction
Apply a vendor or distribution kernel update containing the applicable stable fix.
Check distribution advisories because kernel fixes may be backported without matching upstream version numbers.
Prioritize multi-user systems where untrusted local users can access relevant TPM functionality.
Use normal change controls and reboot into the updated kernel when required.
Validation and detection
Record the running kernel and installed distribution package versions.
Confirm whether the package includes an applicable referenced stable-kernel fix.
Verify the system booted the updated kernel after remediation.
Retest relevant TPM-backed authentication or key-management workflows.
Document systems whose affected status remains uncertain due to backport ambiguity.
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-2025-68792 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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.