From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80832: crypto: qce - fix CCM AAD buffer underallocation
Date: Fri, 4 Sep 2026 17:52:59 +0200 [thread overview]
Message-ID: <2026090456-CVE-2026-80832-a194@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-80832 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 5.15.220 with commit 11775b35ce9f27e73d62188d7d38aa0dc0a219aa
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 6.1.187 with commit c9e0f06a023107694698a7930616aeb460d91816
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 6.6.156 with commit cc56d2b0d77cfeea061e98114992ee687d5eb4dd
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 6.12.108 with commit 002f1f99aef7ea631cb687fc17bce64e4963f6aa
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 6.18.49 with commit 2f65718b9c1095eef1ae9b374aa0384b1b083f3c
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 7.1.13 with commit 46a84efe2dbaddde89073a3c00c694486937c34b
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 7.2.3 with commit 4839f4c21f9c577eedef2919ced878a3057c7fc3
Issue introduced in 5.14 with commit 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 and fixed in 7.3-rc1 with commit 7f2345f47dd189625f657cd72437179ab4170ee1
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80832
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/crypto/qce/aead.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/11775b35ce9f27e73d62188d7d38aa0dc0a219aa
https://git.kernel.org/stable/c/c9e0f06a023107694698a7930616aeb460d91816
https://git.kernel.org/stable/c/cc56d2b0d77cfeea061e98114992ee687d5eb4dd
https://git.kernel.org/stable/c/002f1f99aef7ea631cb687fc17bce64e4963f6aa
https://git.kernel.org/stable/c/2f65718b9c1095eef1ae9b374aa0384b1b083f3c
https://git.kernel.org/stable/c/46a84efe2dbaddde89073a3c00c694486937c34b
https://git.kernel.org/stable/c/4839f4c21f9c577eedef2919ced878a3057c7fc3
https://git.kernel.org/stable/c/7f2345f47dd189625f657cd72437179ab4170ee1
reply other threads:[~2026-09-04 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026090456-CVE-2026-80832-a194@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.