# CVE-2025-68347: ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events

> A buffer overflow in the Linux kernel's ALSA firewire-motu driver allows local attackers to potentially execute code or escalate privileges via crafted DSP events.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 24 Dec 2025
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-73096, BELL-CVE-2025-68347, DEBIAN-CVE-2025-68347, GHSA-h6xr-332m-px9v, ROOT-OS-UBUNTU-2404-CVE-2025-68347, UBUNTU-CVE-2025-68347

## What is CVE-2025-68347?

CVE-2025-68347 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 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:

ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events

The DSP event handling code in hwdep_read() could write more bytes to
the user buffer than requested, when a user provides a buffer smaller
than the event header size (8 bytes).

Fix by using min_t() to clamp the copy size, This ensures we never copy
more than the user requested.

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


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

Apply the vendor's patch.

## Is CVE-2025-68347 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68347 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 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-2025-68347 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-68347/ (Markdown: https://insights.sbomify.com/CVE-2025-68347/index.md)
```

## Sources

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

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