ALSA: usb-audio: Kill timer properly at removal
Summary
| CVE | CVE-2025-38105 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-07-03 09:15:23 UTC |
| Updated | 2026-06-01 17:16:34 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Kill timer properly at removal The USB-audio MIDI code initializes the timer, but in a rare case, the driver might be freed without the disconnect call. This leaves the timer in an active state while the assigned object is released via snd_usbmidi_free(), which ends up with a kernel warning when the debug configuration is enabled, as spotted by fuzzer. For avoiding the problem, put timer_shutdown_sync() at snd_usbmidi_free(), so that the timer can be killed properly. While we're at it, replace the existing timer_delete_sync() at the disconnect callback with timer_shutdown_sync(), too. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected c88469704d63787e8d44ca5ea1c1bd0adc29572d 06513dd6d32c37d0364db8488cfdf3e14da238a8 git | Not specified |
| CNA | Linux | Linux | affected c88469704d63787e8d44ca5ea1c1bd0adc29572d efaf61052b8ff9ee8968912fbaf02c2847c78ede git | Not specified |
| CNA | Linux | Linux | affected c88469704d63787e8d44ca5ea1c1bd0adc29572d 647410a7da46067953a53c0d03f8680eff570959 git | Not specified |
| CNA | Linux | Linux | affected c88469704d63787e8d44ca5ea1c1bd0adc29572d c611b9e55174e439dcd85a72969b43a95f3827a4 git | Not specified |
| CNA | Linux | Linux | affected c88469704d63787e8d44ca5ea1c1bd0adc29572d 62066758d2ae169278e5d6aea5995b1b6f6ddeb5 git | Not specified |
| CNA | Linux | Linux | affected c88469704d63787e8d44ca5ea1c1bd0adc29572d 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1 git | Not specified |
| CNA | Linux | Linux | affected 2.6.14 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.14 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.209 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.111 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.52 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.15.3 6.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.16 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/647410a7da46067953a53c0d03f8680eff570959 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/c611b9e55174e439dcd85a72969b43a95f3827a4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/62066758d2ae169278e5d6aea5995b1b6f6ddeb5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/06513dd6d32c37d0364db8488cfdf3e14da238a8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/efaf61052b8ff9ee8968912fbaf02c2847c78ede | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.