CVE-2026-80832

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 4, 2026

References (8)

Vendor Advisories for CVE-2026-80832(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)6.1.187-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——

Data Freshness Timeline

(refreshed 11× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:32 UTCVendor advisory
  3. 2026-09-18 06:32 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 13:19 UTCVendor advisory
  7. 2026-09-15 13:19 UTCGHSA enrichment
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-12 20:06 UTCVendor advisory
  11. 2026-09-12 20:06 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 02:52 UTCGHSA enrichment
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 09:39 UTCEG score recompute
  17. 2026-09-07 09:39 UTCVendor advisory
  18. 2026-09-07 09:38 UTCGHSA enrichment
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-04 16:22 UTCNVD update
  22. 2026-09-04 16:05 UTCEG score recompute
  23. 2026-09-04 16:04 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80832?
CVE-2026-80832 is a publicly disclosed vulnerability published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: qce - fix CCM AAD buffer underallocation The AAD buffer allocated in qceaeadccmpreparebuf_assoclen() can be smaller than the length later programmed into the DMA scatterlist. The allocation size is currently calculated as:…
When was CVE-2026-80832 disclosed?
CVE-2026-80832 was first published in the National Vulnerability Database on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80832 actively exploited?
CVE-2026-80832 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.4% of all scored CVEs.
How do I remediate CVE-2026-80832?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80832, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80832

Explore →

Is Your Infrastructure Affected by CVE-2026-80832?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs