# CVE-2024-56657: ALSA: control: Avoid WARN() for symlink errors

> A Linux kernel ALSA control issue caused excessive warnings on symlink errors, potentially confusing fuzzers and leading to denial of service.

- **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:** 27 Dec 2024
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-54804, AZL-54842, BELL-CVE-2024-56657, DEBIAN-CVE-2024-56657, GHSA-xpv3-x3xh-h28r, ROOT-OS-DEBIAN-12-CVE-2024-56657, ROOT-OS-UBUNTU-2204-CVE-2024-56657, UBUNTU-CVE-2024-56657

## What is CVE-2024-56657?

CVE-2024-56657 is a medium-severity denial of service vulnerability in Linux kernel, published on 27 Dec 2024. 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:

ALSA: control: Avoid WARN() for symlink errors

Using WARN() for showing the error of symlink creations don't give
more information than telling that something goes wrong, since the
usual code path is a lregister callback from each control element
creation.  More badly, the use of WARN() rather confuses fuzzer as if
it were serious issues.

This patch downgrades the warning messages to use the normal dev_err()
instead of WARN().  For making it clearer, add the function name to
the prefix, too.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-56657 being exploited?

There is no known exploitation of CVE-2024-56657 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-56657 and fix it if it is affected.

What it is: CVE-2024-56657 is a medium-severity denial of service vulnerability in Linux kernel, published on 27 Dec 2024. 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-56657 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-56657/ (Markdown: https://insights.sbomify.com/CVE-2024-56657/index.md)
```

## Sources

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

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