# CVE-2026-80522: crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req()


- **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
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-80522, DEBIAN-CVE-2026-80522, GHSA-fhv2-cf5f-4mpm, UBUNTU-CVE-2026-80522

## What is CVE-2026-80522?

CVE-2026-80522 is a high-severity vulnerability in Linux, published on 26 Aug 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

crypto: tegra - fix rctx->cryptlen calculation in tegra_gcm_do_one_req()

Perform rctx->cryptlen calculation in tegra_gcm_do_one_req() the same way
it is done in tegra_ccm_crypt_init(). The current formulae may lead to a
crash if a caller does not call tegra_gcm_setauthsize() and so ctx->authsize
remains zero. Then a decrypt operation with incorrect rctx->cryptlen will
lead to a write beyound rctx->dst_sg buffer.

As a follow-up cleanup delete struct tegra_aead_ctx->authsize field since
it appears to be completely unused. Also simplify tegra_ccm_setauthsize()
and tegra_gcm_setauthsize() functions respectively.

## Which versions are affected by CVE-2026-80522?


## How do I fix CVE-2026-80522?

Upgrade to a fixed version.

## Is CVE-2026-80522 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80522 and fix it if it is affected.

What it is: CVE-2026-80522 is a high-severity vulnerability in Linux, published on 26 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-80522 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-2026-80522/ (Markdown: https://insights.sbomify.com/CVE-2026-80522/index.md)
```

## Sources

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

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