From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-52972: crypto: af_alg - Cap AEAD AD length to 0x80000000
Date: Wed, 24 Jun 2026 17:29:56 +0100 [thread overview]
Message-ID: <2026062439-CVE-2026-52972-7d96@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: af_alg - Cap AEAD AD length to 0x80000000
In order to prevent arithmetic overflows when checking the TX
buffer size, cap the associated data length to 0x80000000.
The Linux kernel CVE team has assigned CVE-2026-52972 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 5.10.258 with commit f8a5203596797f394ff3f9aa4005597a92249802
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 5.15.209 with commit a9f68d9ed38dd6e5a6c6d75b03d25c1c133e321d
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 6.1.175 with commit a4fe4eb580bbc7439f649a496d4cf38415a4021c
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 6.6.141 with commit e4c4a5074532eaaa14951994a3aad0d479aa7431
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 6.12.91 with commit 265ac26d1c5e17b34d497cbda1f754a1ec8552bc
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 6.18.33 with commit a1c5672faf8e93e38c2deac3979cc767ca5cf918
Issue introduced in 4.1 with commit 400c40cf78da00c16e561a3a253ca272455c42ef and fixed in 7.0.10 with commit 97948906dc8e0ea84775e03e35b60a2063c70193
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-52972
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:
crypto/af_alg.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/f8a5203596797f394ff3f9aa4005597a92249802
https://git.kernel.org/stable/c/a9f68d9ed38dd6e5a6c6d75b03d25c1c133e321d
https://git.kernel.org/stable/c/a4fe4eb580bbc7439f649a496d4cf38415a4021c
https://git.kernel.org/stable/c/e4c4a5074532eaaa14951994a3aad0d479aa7431
https://git.kernel.org/stable/c/265ac26d1c5e17b34d497cbda1f754a1ec8552bc
https://git.kernel.org/stable/c/a1c5672faf8e93e38c2deac3979cc767ca5cf918
https://git.kernel.org/stable/c/97948906dc8e0ea84775e03e35b60a2063c70193
https://git.kernel.org/stable/c/e4c06479d7059888adf2f22bc1ebcf053bf691a2
reply other threads:[~2026-06-24 16:33 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=2026062439-CVE-2026-52972-7d96@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.