linux-cve-announce - CVE-2025-40019: crypto: essiv - Check ssize for decryption and in-place encryption

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: <2025102433-CVE-2025-40019-a8e7@gregkh>
Date: Fri, 24 Oct 2025 13:44:35 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40019: crypto: essiv - Check ssize for decryption and in-place encryption

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

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

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

crypto: essiv - Check ssize for decryption and in-place encryption

Move the ssize check to the start in essiv_aead_crypt so that
it's also checked for decryption and in-place encryption.

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


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

	Issue introduced in 5.4 with commit be1eb7f78aa8fbe34779c56c266ccd0364604e71 and fixed in 5.15.195 with commit df58651968f82344a0ed2afdafd20ecfc55ff548
	Issue introduced in 5.4 with commit be1eb7f78aa8fbe34779c56c266ccd0364604e71 and fixed in 6.1.157 with commit 248ff2797ff52a8cbf86507f9583437443bf7685
	Issue introduced in 5.4 with commit be1eb7f78aa8fbe34779c56c266ccd0364604e71 and fixed in 6.6.113 with commit f37e7860dc5e94c70b4a3e38a5809181310ea9ac
	Issue introduced in 5.4 with commit be1eb7f78aa8fbe34779c56c266ccd0364604e71 and fixed in 6.12.54 with commit dc4c854a5e7453c465fa73b153eba4ef2a240abe
	Issue introduced in 5.4 with commit be1eb7f78aa8fbe34779c56c266ccd0364604e71 and fixed in 6.17.4 with commit da7afb01ba05577ba3629f7f4824205550644986
	Issue introduced in 5.4 with commit be1eb7f78aa8fbe34779c56c266ccd0364604e71 and fixed in 6.18-rc1 with commit 6bb73db6948c2de23e407fe1b7ef94bf02b7529f

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-40019
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/essiv.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/df58651968f82344a0ed2afdafd20ecfc55ff548
	https://git.kernel.org/stable/c/248ff2797ff52a8cbf86507f9583437443bf7685
	https://git.kernel.org/stable/c/f37e7860dc5e94c70b4a3e38a5809181310ea9ac
	https://git.kernel.org/stable/c/dc4c854a5e7453c465fa73b153eba4ef2a240abe
	https://git.kernel.org/stable/c/da7afb01ba05577ba3629f7f4824205550644986
	https://git.kernel.org/stable/c/6bb73db6948c2de23e407fe1b7ef94bf02b7529f