# CVE-2026-80832: crypto: qce - fix CCM AAD buffer underallocation

> A buffer underallocation in the Linux kernel QCE crypto driver allows out-of-bounds reads, potentially causing denial of service or information disclosure.

- **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:** 19 Oct 2026
- **Also known as:** AZL-99567, BELL-CVE-2026-80832, DEBIAN-CVE-2026-80832, GHSA-5ch2-359f-fp8j, UBUNTU-CVE-2026-80832

## What is CVE-2026-80832?

CVE-2026-80832 is a memory corruption vulnerability in Linux, published on 4 Sep 2026. 

### Official description

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

crypto: qce - fix CCM AAD buffer underallocation

The AAD buffer allocated in qce_aead_ccm_prepare_buf_assoclen()
can be smaller than the length later programmed into the DMA
scatterlist.

The allocation size is currently calculated as:

  ALIGN(assoclen, 16) + MAX_CCM_ADATA_HEADER_LEN

while the DMA length is set to:

  ALIGN(assoclen + adata_header_len, 16)

Since ALIGN() does not distribute over addition, the allocation
can be smaller than the DMA length. For example, when
assoclen = 32 and adata_header_len = 2:

  allocation = ALIGN(32, 16) + 6 = 38
  DMA length = ALIGN(32 + 2, 16) = 48

As a result, the QCE hardware can read beyond the allocated
buffer while computing the CBC-MAC over the associated data.
The extra bytes are folded into the authentication tag,
resulting in an incorrect tag and causing CCM self-test
failures such as:

  alg: aead: ccm-aes-qce encryption test failed (wrong result)
  on test vector 8

Fix the allocation by adding the maximum possible AAD header
length before alignment:

  ALIGN(assoclen + MAX_CCM_ADATA_HEADER_LEN, 16)

This guarantees that the allocated buffer is large enough
for the fully padded AAD data for all supported header sizes.

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


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

Apply the vendor's patch.

## Is CVE-2026-80832 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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