# CVE-2024-58077: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback

> A flaw in the Linux kernel's ASoC subsystem allows userspace to trigger excessive logging, potentially causing a denial of service by exhausting disk space or syslog resources.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2024-58077, DEBIAN-CVE-2024-58077, GHSA-23x3-fcgm-qf4c, ROOT-OS-UBUNTU-2204-CVE-2024-58077, ROOT-OS-UBUNTU-2404-CVE-2024-58077, UBUNTU-CVE-2024-58077

## What is CVE-2024-58077?

CVE-2024-58077 is a medium-severity denial of service vulnerability in Linux kernel, published on 6 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2024-58077?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-58077?

Apply the vendor's patch.

## Is CVE-2024-58077 being exploited?

There is no known exploitation of CVE-2024-58077 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58077 and fix it if it is affected.

What it is: CVE-2024-58077 is a medium-severity denial of service vulnerability in Linux kernel, published on 6 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58077 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58077/ (Markdown: https://insights.sbomify.com/CVE-2024-58077/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58077
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58077
- OSV: https://osv.dev/vulnerability/CVE-2024-58077

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58077/
Summaries are generated and may contain mistakes; the official description above is the record.