USB: core: Fix deadlock in usb_deauthorize_interface()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 310d2b4124c073a2057ef9d952d4d938e9b1dfd9 · < 122a06f1068bf5e39089863f4f60b1f5d4273384| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
USB: core: Fix deadlock in usb_deauthorize_interface()
Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface's parent USB device.
The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can't complete until the device lock has been released, and the lock won't be released until the removal has finished.
The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback.
Reported-and-tested by: Yue Sun <samsun1006219@gmail.com> Reported by: xingwei lee <xrivendell7@gmail.com>
From the CVE record · Linux
The Linux kernel’s USB interface authorization callback can deadlock when another process holds the parent USB device lock while removing the interface. A local process accessing the affected sysfs attribute during a configuration change or device disconnection can trigger the deadlock; the input does not specify whether authentication is required.
Engineers running Linux kernels with the affected USB core code should check their versions against the vendor advisory; affected versions are not specified.