crypto: qce - fix CCM AAD buffer underallocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.220, 6.1.187, 6.6.156, 6.12.108, 6.18.49, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in 11775b35ce9f27e73d62188d7d38aa0dc0a219aa; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in c9e0f06a023107694698a7930616aeb460d91816; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in cc56d2b0d77cfeea061e98114992ee687d5eb4dd; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in 002f1f99aef7ea631cb687fc17bce64e4963f6aa; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in 2f65718b9c1095eef1ae9b374aa0384b1b083f3c; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in 46a84efe2dbaddde89073a3c00c694486937c34b; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in 4839f4c21f9c577eedef2919ced878a3057c7fc3; From 9363efb4181c5e0fbf86bdfa759262aa29f0eb50 · fixed in 7f2345f47dd189625f657cd72437179ab4170ee1
- Linux Linux
5.14
- KernelLinux
From 5.14.0 · fixed in 5.15.220; From 5.16.0 · fixed in 6.1.187; From 6.2.0 · fixed in 6.6.156; From 6.7.0 · fixed in 6.12.108; From 6.13.0 · fixed in 6.18.49; From 6.19.0 · fixed in 7.1.13; From 7.2.0 · fixed in 7.2.3
References 8
git.kernel.org
- stable/c/11775b35ce9f27e73d62188d7d38aa0dc0a219aa
- stable/c/c9e0f06a023107694698a7930616aeb460d91816
- stable/c/cc56d2b0d77cfeea061e98114992ee687d5eb4dd
- stable/c/002f1f99aef7ea631cb687fc17bce64e4963f6aa
- stable/c/2f65718b9c1095eef1ae9b374aa0384b1b083f3c
- stable/c/46a84efe2dbaddde89073a3c00c694486937c34b
- stable/c/4839f4c21f9c577eedef2919ced878a3057c7fc3
- stable/c/7f2345f47dd189625f657cd72437179ab4170ee1