ALSA: usb-audio: Kill timer properly at removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c88469704d63787e8d44ca5ea1c1bd0adc29572d · < 0718a78f6a9f04b88d0dc9616cc216b31c5f3cf1| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ALSA USB-audio MIDI code can leave a timer active if the driver is freed without a disconnect call. When the timer’s object is released, this can trigger a kernel warning with debug configuration enabled. The input does not describe an attacker or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with ALSA USB-audio MIDI support should check their kernel version; affected versions are not specified.