# CVE-2026-80882: crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm

> A missing error check in the Linux kernel's Tegra CCM crypto driver can cause a denial of service when input buffer allocation fails.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-80882, DEBIAN-CVE-2026-80882, GHSA-qc8g-564w-4r6x, UBUNTU-CVE-2026-80882

## What is CVE-2026-80882?

CVE-2026-80882 is a denial of service vulnerability in Linux, published on 4 Sep 2026. 

### Official description

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

crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm

Ensure the ENOMEM error value is set when the input buffer allocation
fails in tegra_ccm_do_one_req.

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


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

Apply the vendor's patch.

## Is CVE-2026-80882 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80882 is a denial of service vulnerability in Linux, published on 4 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-80882 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-80882/ (Markdown: https://insights.sbomify.com/CVE-2026-80882/index.md)
```

## Sources

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

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