# CVE-2024-39491: ALSA: hda: cs35l56: Fix lifetime of cs_dsp instance

> A use-after-free vulnerability in the Linux kernel's cs35l56 audio driver allows attackers to cause denial of service or execute arbitrary code via improper memory management during driver unbinding.

- **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:** 10 Jul 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2024-39491, DEBIAN-CVE-2024-39491, GHSA-wvx8-cjrx-23xg, UBUNTU-CVE-2024-39491

## What is CVE-2024-39491?

CVE-2024-39491 is a medium-severity use after free vulnerability in Linux kernel, published on 10 Jul 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: hda: cs35l56: Fix lifetime of cs_dsp instance

The cs_dsp instance is initialized in the driver probe() so it
should be freed in the driver remove(). Also fix a missing call
to cs_dsp_remove() in the error path of cs35l56_hda_common_probe().

The call to cs_dsp_remove() was being done in the component unbind
callback cs35l56_hda_unbind(). This meant that if the driver was
unbound and then re-bound it would be using an uninitialized cs_dsp
instance.

It is best to initialize the cs_dsp instance in probe() so that it
can return an error if it fails. The component binding API doesn't
have any error handling so there's no way to handle a failure if
cs_dsp was initialized in the bind.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-39491 being exploited?

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

What it is: CVE-2024-39491 is a medium-severity use after free vulnerability in Linux kernel, published on 10 Jul 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-39491 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-39491/ (Markdown: https://insights.sbomify.com/CVE-2024-39491/index.md)
```

## Sources

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

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