Subject: CVE-2024-38551: ASoC: mediatek: Assign dummy when codec not specified for a DAI link

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

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

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

ASoC: mediatek: Assign dummy when codec not specified for a DAI link

MediaTek sound card drivers are checking whether a DAI link is present
and used on a board to assign the correct parameters and this is done
by checking the codec DAI names at probe time.

If no real codec is present, assign the dummy codec to the DAI link
to avoid NULL pointer during string comparison.

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

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

	Issue introduced in 6.3 with commit 4302187d955f and fixed in 6.6.33 with commit 87b8dca6e06f
	Issue introduced in 6.3 with commit 4302187d955f and fixed in 6.8.12 with commit cbbcabc7f097
	Issue introduced in 6.3 with commit 4302187d955f and fixed in 6.9.3 with commit 0c052b1c11d8
	Issue introduced in 6.3 with commit 4302187d955f and fixed in 6.10 with commit 5f39231888c6

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-38551
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/mediatek/common/mtk-soundcard-driver.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/87b8dca6e06f9b1681bc52bf7bfa85c663a11158
	https://git.kernel.org/stable/c/cbbcabc7f0979f6542372cf88d7a9da7143a4226
	https://git.kernel.org/stable/c/0c052b1c11d8119f3048b1f7b3c39a90500cacf9
	https://git.kernel.org/stable/c/5f39231888c63f0a7708abc86b51b847476379d8