CVE-2026-80832 — crypto: qce - fix CCM AAD buffer underallocation
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < 11775b35ce9f27e73d62188d7d38aa0dc0a219aa≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < c9e0f06a023107694698a7930616aeb460d91816≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < cc56d2b0d77cfeea061e98114992ee687d5eb4dd≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < 002f1f99aef7ea631cb687fc17bce64e4963f6aa≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < 2f65718b9c1095eef1ae9b374aa0384b1b083f3c≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < 46a84efe2dbaddde89073a3c00c694486937c34b≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < 4839f4c21f9c577eedef2919ced878a3057c7fc3≥ 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and < 7f2345f47dd189625f657cd72437179ab4170ee1 and 1 moreversion 5.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 25, 2026 · 10 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- github.com/advisories/GHSA-5ch2-359f-fp8j
- git.kernel.org/stable/c/4839f4c21f9c577eedef2919ced878a3057c7fc3
- git.kernel.org/stable/c/7f2345f47dd189625f657cd72437179ab4170ee1
- git.kernel.org/stable/c/2f65718b9c1095eef1ae9b374aa0384b1b083f3c
- git.kernel.org/stable/c/cc56d2b0d77cfeea061e98114992ee687d5eb4dd
- git.kernel.org/stable/c/46a84efe2dbaddde89073a3c00c694486937c34b
- git.kernel.org/stable/c/c9e0f06a023107694698a7930616aeb460d91816
- git.kernel.org/stable/c/002f1f99aef7ea631cb687fc17bce64e4963f6aa
- nvd.nist.gov/vuln/detail/CVE-2026-80832
- git.kernel.org/stable/c/11775b35ce9f27e73d62188d7d38aa0dc0a219aa
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 12h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 12h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 12h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 12h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 12h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 12h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80832 is "crypto: qce - fix CCM AAD buffer underallocation", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.