linux-cve-announce - CVE-2025-37808: crypto: null - Use spin lock instead of mutex

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: <2025050816-CVE-2025-37808-57bb@gregkh>
Date: Thu,  8 May 2025 08:39:17 +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-37808: crypto: null - Use spin lock instead of mutex

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

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

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

crypto: null - Use spin lock instead of mutex

As the null algorithm may be freed in softirq context through
af_alg, use spin locks instead of mutexes to protect the default
null algorithm.

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


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

	Fixed in 5.4.293 with commit f7a5a5c8e1ec16a4b2041398abe95de0e14572ef
	Fixed in 5.10.237 with commit e307c54ac8198bf09652c72603ba6e6d97798410
	Fixed in 5.15.181 with commit 1dd4a8561d85dea545cf93f56efc48df8176e218
	Fixed in 6.1.136 with commit e27244cbe10658a66b8775be7f0acc4ad2f618d6
	Fixed in 6.6.89 with commit 1b66a5920b7fc7cc6251192a3fcad115b6d75dd5
	Fixed in 6.12.26 with commit 0486de3c1b8223138dcc614846bd76364f758de6
	Fixed in 6.14.5 with commit 8cf2945512a8c0ef74ddd5b5a4f6b6a2fb1a4efb
	Fixed in 6.15-rc1 with commit dcc47a028c24e793ce6d6efebfef1a1e92f80297

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-37808
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/crypto_null.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/f7a5a5c8e1ec16a4b2041398abe95de0e14572ef
	https://git.kernel.org/stable/c/e307c54ac8198bf09652c72603ba6e6d97798410
	https://git.kernel.org/stable/c/1dd4a8561d85dea545cf93f56efc48df8176e218
	https://git.kernel.org/stable/c/e27244cbe10658a66b8775be7f0acc4ad2f618d6
	https://git.kernel.org/stable/c/1b66a5920b7fc7cc6251192a3fcad115b6d75dd5
	https://git.kernel.org/stable/c/0486de3c1b8223138dcc614846bd76364f758de6
	https://git.kernel.org/stable/c/8cf2945512a8c0ef74ddd5b5a4f6b6a2fb1a4efb
	https://git.kernel.org/stable/c/dcc47a028c24e793ce6d6efebfef1a1e92f80297