# CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size

> An out-of-bounds indexing flaw in the Linux kernel TPM2 sessions allows attackers to cause memory corruption, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-68792, DEBIAN-CVE-2025-68792, GHSA-2wfq-pvgx-w5wx, UBUNTU-CVE-2025-68792

## What is CVE-2025-68792?

CVE-2025-68792 is a high-severity memory corruption vulnerability in Linux, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2025-68792?


## How do I fix CVE-2025-68792?

Apply the vendor's patch.

## Is CVE-2025-68792 being exploited?

There is no known exploitation of CVE-2025-68792 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68792 and fix it if it is affected.

What it is: CVE-2025-68792 is a high-severity memory corruption vulnerability in Linux, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68792 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68792/ (Markdown: https://insights.sbomify.com/CVE-2025-68792/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68792
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68792
- OSV: https://osv.dev/vulnerability/CVE-2025-68792

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68792/
Summaries are generated and may contain mistakes; the official description above is the record.