ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ASoC soc-pcm code can log errors triggered by invalid parameters from userspace during the .prepare callback. A local user could repeatedly trigger those errors to fill the syslog or disk space, causing a denial of service.
Anyone running a Linux kernel with the affected ASoC soc-pcm code should check their kernel against the vendor advisory; affected versions were not provided.