Subject: CVE-2024-47730: crypto: hisilicon/qm - inject error before stopping queue

From: Greg Kroah-Hartman <[email-masked]>

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

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

crypto: hisilicon/qm - inject error before stopping queue

The master ooo cannot be completely closed when the
accelerator core reports memory error. Therefore, the driver
needs to inject the qm error to close the master ooo. Currently,
the qm error is injected after stopping queue, memory may be
released immediately after stopping queue, causing the device to
access the released memory. Therefore, error is injected to close master
ooo before stopping queue to ensure that the device does not access
the released memory.

The Linux kernel CVE team has assigned CVE-2024-47730 to this issue.

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

	Issue introduced in 5.8 with commit 6c6dd5802c2d and fixed in 6.1.113 with commit 98d3be34c915
	Issue introduced in 5.8 with commit 6c6dd5802c2d and fixed in 6.6.54 with commit aa3e0db35a60
	Issue introduced in 5.8 with commit 6c6dd5802c2d and fixed in 6.10.13 with commit f8024f12752e
	Issue introduced in 5.8 with commit 6c6dd5802c2d and fixed in 6.11.2 with commit c5f5b813e546
	Issue introduced in 5.8 with commit 6c6dd5802c2d and fixed in 6.12-rc1 with commit b04f06fc0243

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-2024-47730
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/qm.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/98d3be34c9153eceadb56de50d9f9347e88d86e4
	https://git.kernel.org/stable/c/aa3e0db35a60002fb34ef0e4ad203aa59fd00203
	https://git.kernel.org/stable/c/f8024f12752e32ffbbf59e1c09d949f977ff743f
	https://git.kernel.org/stable/c/c5f5b813e546f7fe133539c3d7a5086cc8dd2aa1
	https://git.kernel.org/stable/c/b04f06fc0243600665b3b50253869533b7938468