linux-cve-announce - CVE-2025-68726: crypto: aead

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025122405-CVE-2025-68726-7aff@gregkh>
Date: Wed, 24 Dec 2025 11:35:28 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68726: crypto: aead - Fix reqsize handling

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

crypto: aead - Fix reqsize handling

Commit afddce13ce81d ("crypto: api - Add reqsize to crypto_alg")
introduced cra_reqsize field in crypto_alg struct to replace type
specific reqsize fields. It looks like this was introduced specifically
for ahash and acomp from the commit description as subsequent commits
add necessary changes in these alg frameworks.

However, this is being recommended for use in all crypto algs
instead of setting reqsize using crypto_*_set_reqsize(). Using
cra_reqsize in aead algorithms, hence, causes memory corruptions and
crashes as the underlying functions in the algorithm framework have not
been updated to set the reqsize properly from cra_reqsize. [1]

Add proper set_reqsize calls in the aead init function to properly
initialize reqsize for these algorithms in the framework.

[1]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b

The Linux kernel CVE team has assigned CVE-2025-68726 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 6.16 with commit afddce13ce81d52a13898fa0700917835c71acd6 and fixed in 6.17.13 with commit 64377e66e187164bd6737112d07257f5f0feb681
	Issue introduced in 6.16 with commit afddce13ce81d52a13898fa0700917835c71acd6 and fixed in 6.18.2 with commit 12b413f5460c393d1151a37f591140693eca0f84
	Issue introduced in 6.16 with commit afddce13ce81d52a13898fa0700917835c71acd6 and fixed in 6.19-rc1 with commit 9b04d8f00569573796dd05397f5779135593eb24

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-2025-68726
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/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/64377e66e187164bd6737112d07257f5f0feb681
	https://git.kernel.org/stable/c/12b413f5460c393d1151a37f591140693eca0f84
	https://git.kernel.org/stable/c/9b04d8f00569573796dd05397f5779135593eb24