CVE-2026-97407: ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt

CVE-2026-97407: ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt

[Greg Kroah-Hartman]

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

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

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

ASoC: rockchip: rockchip_pdm: Handle runtime PM resume failures in set_fmt

rockchip_pdm_set_fmt() calls pm_runtime_get_sync() before accessing
hardware registers, but ignores its return value.
If the runtime resume fails, the function continues to perform register
accesses while the device state is undefined.
Replace pm_runtime_get_sync() with pm_runtime_resume_and_get() and
return early on failure to avoid unpowered register accesses.

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


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

	Fixed in 6.12.111 with commit a9cc27a4a9b5fe013e152841fd8408061fa2312f
	Fixed in 6.18.53 with commit b2b5c2ca5a4924271fa86d75a252de32fa285375
	Fixed in 7.2 with commit ee7b5f7b39332febf917f9ebf212842cc9379815

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-97407
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:
	sound/soc/rockchip/rockchip_pdm.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/a9cc27a4a9b5fe013e152841fd8408061fa2312f
	https://git.kernel.org/stable/c/b2b5c2ca5a4924271fa86d75a252de32fa285375
	https://git.kernel.org/stable/c/ee7b5f7b39332febf917f9ebf212842cc9379815