Metrics
Affected Vendors & Products
Wed, 25 Mar 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 20 Nov 2025 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | NVD-CWE-noinfo | |
| CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
cvssV3_1
|
Sun, 12 Oct 2025 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Fri, 04 Jul 2025 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Thu, 03 Jul 2025 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | ALSA: usb-audio: Kill timer properly at removal | |
| References |
|
Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2026-03-25T10:19:23.151Z
Reserved: 2025-04-16T04:51:23.985Z
Link: CVE-2025-38105
No data.
Status : Modified
Published: 2025-07-03T09:15:23.997
Modified: 2026-03-25T11:16:10.130
Link: CVE-2025-38105
OpenCVE Enrichment
Updated: 2025-07-06T22:16:21Z