From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53016: crypto: ccp - copy IV using skcipher ivsize
Date: Wed, 24 Jun 2026 17:30:40 +0100 [thread overview]
Message-ID: <2026062451-CVE-2026-53016-90ac@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: ccp - copy IV using skcipher ivsize
AF_ALG rfc3686-ctr-aes-ccp requests pass an 8-byte IV to the driver.
ccp_aes_complete() restores AES_BLOCK_SIZE bytes into the caller's IV
buffer while RFC3686 skciphers expose an 8-byte IV, so the restore
overruns the provided buffer.
Use crypto_skcipher_ivsize() to copy only the algorithm's IV length.
The Linux kernel CVE team has assigned CVE-2026-53016 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 5.10.258 with commit 939061b2d0f7f15114e34b4ce878ef50ff4089c3
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 5.15.209 with commit 798d409a8949f3f495f238549b86de2886b129bd
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 6.1.175 with commit dfb2cf434829819268fe50f41542aad318ad62b2
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 6.6.141 with commit eecee15e263ccb8cd77170a56ab6c969cb54dd6a
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 6.12.91 with commit bb01d8f1f385bc9034ca114d3508c7fdea24fc9a
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 6.18.33 with commit df9784bb5b637ac80f4a2768a58ca9a50bef28a9
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 7.0.10 with commit 227c1e1d9e2aa4cfc65ba446d5690da1f546cda4
Issue introduced in 3.14 with commit 2b789435d7f36ed918d92db647f3a2f3fec9bb1f and fixed in 7.1 with commit a7a1f3cdd64d8a165d9b8c9e9ad7fb46ac19dfc4
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-53016
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/ccp/ccp-crypto-aes.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/939061b2d0f7f15114e34b4ce878ef50ff4089c3
https://git.kernel.org/stable/c/798d409a8949f3f495f238549b86de2886b129bd
https://git.kernel.org/stable/c/dfb2cf434829819268fe50f41542aad318ad62b2
https://git.kernel.org/stable/c/eecee15e263ccb8cd77170a56ab6c969cb54dd6a
https://git.kernel.org/stable/c/bb01d8f1f385bc9034ca114d3508c7fdea24fc9a
https://git.kernel.org/stable/c/df9784bb5b637ac80f4a2768a58ca9a50bef28a9
https://git.kernel.org/stable/c/227c1e1d9e2aa4cfc65ba446d5690da1f546cda4
https://git.kernel.org/stable/c/a7a1f3cdd64d8a165d9b8c9e9ad7fb46ac19dfc4
reply other threads:[~2026-06-24 16:35 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=2026062451-CVE-2026-53016-90ac@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.