cve/2024/CVE-2024-58077.md

### [CVE-2024-58077](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-58077)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=1f566435141047ca7db26aa4b0b6647a25badaee%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=6.5%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### Description

In the Linux kernel, the following vulnerability has been resolved:ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callbackcommit 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 usedupon invalid parameters coming from userspace and in that case we don'twant to log an error since we do not want to give userspace a way to doa denial-of-service attack on the syslog / diskspace.So don't use soc_pcm_ret() on .prepare callback is better idea.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/fkie-cad/nvd-json-data-feeds
- https://github.com/w4zu/Debian_security