ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 301c26a018acb94dd537a4418cefa0f654500c6f, Kernel 79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee, Kernel 8ec4e8c8e142933eaa8e1ed87168831069250e4e and 1 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.5, >=1f566435141047ca7db26aa4b0b6647a25badaee <301c26a018acb94dd537a4418cefa0f654500c6f, >=1f566435141047ca7db26aa4b0b6647a25badaee <79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee, >=1f566435141047ca7db26aa4b0b6647a25badaee <8ec4e8c8e142933eaa8e1ed87168831069250e4e, >=1f566435141047ca7db26aa4b0b6647a25badaee <90778f31efdf44622065ebbe8d228284104bd26f | 301c26a018acb94dd537a4418cefa0f654500c6f, 79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee, 8ec4e8c8e142933eaa8e1ed87168831069250e4e, 90778f31efdf44622065ebbe8d228284104bd26f |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket