# CVE-2025-68346: ALSA: dice: fix buffer overflow in detect_stream_formats()

> A malicious FireWire device can trigger a buffer overflow in the Linux kernel ALSA driver, potentially allowing code execution or system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68346, DEBIAN-CVE-2025-68346, GHSA-f579-g3c4-8j5j, ROOT-OS-DEBIAN-11-CVE-2025-68346, ROOT-OS-DEBIAN-12-CVE-2025-68346, ROOT-OS-DEBIAN-13-CVE-2025-68346, ROOT-OS-UBUNTU-2204-CVE-2025-68346, ROOT-OS-UBUNTU-2404-CVE-2025-68346, UBUNTU-CVE-2025-68346

## What is CVE-2025-68346?

CVE-2025-68346 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ALSA: dice: fix buffer overflow in detect_stream_formats()

The function detect_stream_formats() reads the stream_count value directly
from a FireWire device without validating it. This can lead to
out-of-bounds writes when a malicious device provides a stream_count value
greater than MAX_STREAMS.

Fix by applying the same validation to both TX and RX stream counts in
detect_stream_formats().

## Which versions are affected by CVE-2025-68346?


## How do I fix CVE-2025-68346?

Apply the vendor's patch.

## Is CVE-2025-68346 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68346 and fix it if it is affected.

What it is: CVE-2025-68346 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-68346 in the wild and no public exploit code.

Affected product: Linux. 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-2025-68346/ (Markdown: https://insights.sbomify.com/CVE-2025-68346/index.md)
```

## Sources

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

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