# CVE-2026-96675: alsa-lib through 1.2.16.1 Denial of Service via pcm_multi

> Attackers can cause a denial of service in applications using alsa-lib by providing a malicious configuration file that triggers an assertion failure.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** AZL-105057, DEBIAN-CVE-2026-96675, ECHO-9212-44dc-f572, GHSA-3gf2-g4r5-8vxr, UBUNTU-CVE-2026-96675

## What is CVE-2026-96675?

CVE-2026-96675 is a medium-severity denial of service vulnerability in alsa-lib, published on 23 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

alsa-lib through 1.2.16.1 contains a denial of service vulnerability in the multi PCM plugin that fails to validate sparse binding indices before array access. Attackers can supply a malicious ALSA configuration file with sparse bindings to trigger an out-of-bounds array read and assertion failure, causing the application to abort.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2026-96675?


## How do I fix CVE-2026-96675?

Apply the vendor's patch.

## Is CVE-2026-96675 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96675 and fix it if it is affected.

What it is: CVE-2026-96675 is a medium-severity denial of service vulnerability in alsa-lib, published on 23 Sep 2026. 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-2026-96675 in the wild and no public exploit code.

Affected product: alsa-lib. 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-2026-96675/ (Markdown: https://insights.sbomify.com/CVE-2026-96675/index.md)
```

## Sources

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

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