CVE-2026-80832

crypto: qce - fix CCM AAD buffer underallocation

N/A
Published: September 4, 2026 at 03:54 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.149363efb4181c5e0fbf86bdfa759262aa29f0eb50
Vendor states this is fixed in 002f1f99aef7ea631cb687fc17bce64e4963f6aa (fixed)
Vendor states this is fixed in 11775b35ce9f27e73d62188d7d38aa0dc0a219aa (fixed)
Vendor states this is fixed in 2f65718b9c1095eef1ae9b374aa0384b1b083f3c (fixed)
Vendor states this is fixed in 46a84efe2dbaddde89073a3c00c694486937c34b (fixed)
Vendor states this is fixed in 4839f4c21f9c577eedef2919ced878a3057c7fc3 (fixed)
Vendor states this is fixed in 7f2345f47dd189625f657cd72437179ab4170ee1 (fixed)
Vendor states this is fixed in c9e0f06a023107694698a7930616aeb460d91816 (fixed)
Vendor states this is fixed in cc56d2b0d77cfeea061e98114992ee687d5eb4dd (fixed)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card