CVE-2026-74353: drm/amdkfd: always resume_all after suspend_all

CVE-2026-74353: drm/amdkfd: always resume_all after suspend_all

[Greg Kroah-Hartman]

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

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

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

drm/amdkfd: always resume_all after suspend_all

Need to restore any good queues even if the suspend_all
failed for some.  Always run remove_queue as that will
schedule a GPU reset is removing the queue fails.

v2: move resume_all after remove

The Linux kernel CVE team has assigned CVE-2026-74353 to this issue.


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

	Issue introduced in 6.12 with commit eb067d65c33eecd4b81771384183ad42eec259bf and fixed in 6.12.97 with commit e29da2a4d9a3b1837dec3ce0892835d506c2a85e
	Issue introduced in 6.12 with commit eb067d65c33eecd4b81771384183ad42eec259bf and fixed in 6.18.40 with commit 9a030fcb4b192a508113787ef28fb97e27dcf6f6
	Issue introduced in 6.12 with commit eb067d65c33eecd4b81771384183ad42eec259bf and fixed in 7.1.5 with commit b5fc19c898e08deb40b671329d99d85d2d575f0b
	Issue introduced in 6.12 with commit eb067d65c33eecd4b81771384183ad42eec259bf and fixed in 7.2-rc1 with commit 56ae73c92e200e630c2bdf1e98c88b86c8483b37

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-2026-74353
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/gpu/drm/amd/amdkfd/kfd_device_queue_manager.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/e29da2a4d9a3b1837dec3ce0892835d506c2a85e
	https://git.kernel.org/stable/c/9a030fcb4b192a508113787ef28fb97e27dcf6f6
	https://git.kernel.org/stable/c/b5fc19c898e08deb40b671329d99d85d2d575f0b
	https://git.kernel.org/stable/c/56ae73c92e200e630c2bdf1e98c88b86c8483b37