linux-cve-announce - CVE-2025-40062: crypto: hisilicon/qm

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: <2025102816-CVE-2025-40062-9b53@gregkh>
Date: Tue, 28 Oct 2025 12:48:39 +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-40062: crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs

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

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

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

crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs

When the initialization of qm->debug.acc_diff_reg fails,
the probe process does not exit. However, after qm->debug.qm_diff_regs is
freed, it is not set to NULL. This can lead to a double free when the
remove process attempts to free it again. Therefore, qm->debug.qm_diff_regs
should be set to NULL after it is freed.

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


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

	Issue introduced in 6.1.98 with commit eda60520cfe3aba9f088c68ebd5bcbca9fc6ac3c and fixed in 6.1.156 with commit a7836260d5121949ba734e840d42a86ab4a32fcc
	Issue introduced in 6.6.39 with commit 7fc8d9a525b5c3f8dfa5ed50901e764d8ede7e1e and fixed in 6.6.112 with commit 1750f1ec143ebabdbdfa013668665c9d5042c430
	Issue introduced in 6.10 with commit 8be0913389718e8d27c4f1d4537b5e1b99ed7739 and fixed in 6.12.53 with commit a87a21a56244b8f4eb357f6bad879247005bbe38
	Issue introduced in 6.10 with commit 8be0913389718e8d27c4f1d4537b5e1b99ed7739 and fixed in 6.17.3 with commit 7226a0650ad5705bd8d39a11be270fa21ed1e6a5
	Issue introduced in 6.10 with commit 8be0913389718e8d27c4f1d4537b5e1b99ed7739 and fixed in 6.18-rc1 with commit f0cafb02de883b3b413d34eb079c9680782a9cc1
	Issue introduced in 6.9.9 with commit e0a2d2df9ba7bd6bd7e0a9b6a5e3894f7e8445b3

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-40062
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/hisilicon/debugfs.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/a7836260d5121949ba734e840d42a86ab4a32fcc
	https://git.kernel.org/stable/c/1750f1ec143ebabdbdfa013668665c9d5042c430
	https://git.kernel.org/stable/c/a87a21a56244b8f4eb357f6bad879247005bbe38
	https://git.kernel.org/stable/c/7226a0650ad5705bd8d39a11be270fa21ed1e6a5
	https://git.kernel.org/stable/c/f0cafb02de883b3b413d34eb079c9680782a9cc1