linux-cve-announce - CVE-2024-58077: ASoC: soc-pcm: don't use soc_pcm

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: <2025030608-CVE-2024-58077-d4e3@gregkh>
Date: Thu,  6 Mar 2025 17:14:10 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-58077: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback

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

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

ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback

commit 1f5664351410 ("ASoC: lower "no backend DAIs enabled for ... Port"
log severity") ignores -EINVAL error message on common soc_pcm_ret().
It is used from many functions, ignoring -EINVAL is over-kill.

The reason why -EINVAL was ignored was it really should only be used
upon invalid parameters coming from userspace and in that case we don't
want to log an error since we do not want to give userspace a way to do
a denial-of-service attack on the syslog / diskspace.

So don't use soc_pcm_ret() on .prepare callback is better idea.

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


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

	Fixed in 6.1.129 with commit b65ba768302adc7ddc70811116cef80ca089af59
	Fixed in 6.6.78 with commit 79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee
	Fixed in 6.12.14 with commit 90778f31efdf44622065ebbe8d228284104bd26f
	Fixed in 6.13.3 with commit 8ec4e8c8e142933eaa8e1ed87168831069250e4e
	Fixed in 6.14-rc1 with commit 301c26a018acb94dd537a4418cefa0f654500c6f

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-58077
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/soc-pcm.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/b65ba768302adc7ddc70811116cef80ca089af59
	https://git.kernel.org/stable/c/79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee
	https://git.kernel.org/stable/c/90778f31efdf44622065ebbe8d228284104bd26f
	https://git.kernel.org/stable/c/8ec4e8c8e142933eaa8e1ed87168831069250e4e
	https://git.kernel.org/stable/c/301c26a018acb94dd537a4418cefa0f654500c6f