# ALSA: usb-audio: Kill timer properly at removal

CVE record · `CVE-2025-38105`

- **Identifiers:** `CVE-2025-38105`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 3 Jul 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 3 Jul 2025, 08:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `c88469704d63787e8d44ca5ea1c1bd0adc29572d to before 06513dd6d32c37d0364db8488cfdf3e14da238a8` (git)
  - affected: `c88469704d63787e8d44ca5ea1c1bd0adc29572d to before efaf61052b8ff9ee8968912fbaf02c2847c78ede` (git)
  - affected: `c88469704d63787e8d44ca5ea1c1bd0adc29572d to before 647410a7da46067953a53c0d03f8680eff570959` (git)
  - affected: `c88469704d63787e8d44ca5ea1c1bd0adc29572d to before c611b9e55174e439dcd85a72969b43a95f3827a4` (git)
  - affected: `c88469704d63787e8d44ca5ea1c1bd0adc29572d to before 62066758d2ae169278e5d6aea5995b1b6f6ddeb5` (git)
  - affected: `c88469704d63787e8d44ca5ea1c1bd0adc29572d to before 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.14`
  - unaffected: `before 2.6.14` (semver)
  - unaffected: `5.15.209 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.167 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.111 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.52 to 6.12.*, inclusive` (semver)
  - unaffected: `6.15.3 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel ALSA usb-audio MIDI driver is affected in several version ranges, starting from commit c88469704d63787e8d44ca5ea1c1bd0adc29572d and in kernels from 2.6.14 onward until fixed. The source describes a timer left active when the driver is freed without a disconnect call, which triggers a kernel warning when debug configuration is enabled. The source gives few details on attacker requirements or impact beyond that warning. Fixed versions are listed as 5.15.209, 6.1.167, 6.6.111, and 6.12.52 and later in their series, so upgrade to a fixed kernel release for your branch.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 9th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 3 Jul 2025, 08:35 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38105)
- 3 Jul 2025, 09:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38105)

## Sources

- [CVE List: CVE-2025-38105](https://www.cve.org/CVERecord?id=CVE-2025-38105)
- [NVD: CVE-2025-38105](https://nvd.nist.gov/vuln/detail/CVE-2025-38105)

### References from the CNA

- <https://git.kernel.org/stable/c/06513dd6d32c37d0364db8488cfdf3e14da238a8>
- <https://git.kernel.org/stable/c/efaf61052b8ff9ee8968912fbaf02c2847c78ede>
- <https://git.kernel.org/stable/c/647410a7da46067953a53c0d03f8680eff570959>
- <https://git.kernel.org/stable/c/c611b9e55174e439dcd85a72969b43a95f3827a4>
- <https://git.kernel.org/stable/c/62066758d2ae169278e5d6aea5995b1b6f6ddeb5>
- <https://git.kernel.org/stable/c/0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-38105>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-38105/>. Everything for agents: <https://agentprime.io/llms.txt>.
