ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.2%
exploitation probability
0.2%top 93% of all CVEs
observed exploitation
nono source reports it
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.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/301c26a018acb94dd537a4418cefa0f654500c6fhttps://git.kernel.org/stable/c/79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9eehttps://git.kernel.org/stable/c/8ec4e8c8e142933eaa8e1ed87168831069250e4ehttps://git.kernel.org/stable/c/90778f31efdf44622065ebbe8d228284104bd26fhttps://lists.debian.org/debian-lts-announce/2025/03/msg00028.html