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.
Metrics
Affected Vendors & Products
References
History
Thu, 19 Jun 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Mon, 26 May 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-400 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Fri, 07 Mar 2025 02:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Thu, 06 Mar 2025 16:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-03-06T16:13:41.159Z
Updated: 2025-06-19T12:56:44.523Z
Reserved: 2025-03-06T15:52:09.183Z
Link: CVE-2024-58077

No data.

Status : Awaiting Analysis
Published: 2025-03-06T17:15:21.123
Modified: 2025-06-19T13:15:51.193
Link: CVE-2024-58077
