usb: gadget: core: flush gadget workqueue after device removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: core: flush gadget workqueue after device removal
device_del() can lead to new work being scheduled in gadget->work workqueue. This is observed, for example, with the dwc3 driver with the following call stack: device_del() gadget_unbind_driver() usb_gadget_disconnect_locked() dwc3_gadget_pullup() dwc3_gadget_soft_disconnect() usb_gadget_set_state() schedule_work(&gadget->work)
Move flush_work() after device_del() to ensure the workqueue is cleaned up.
From the CVE record · Linux
In the Linux kernel USB gadget core, removing a device can schedule new gadget work after the workqueue has been flushed. This can leave work pending after device removal; the input does not specify an attacker action or exploitation conditions.
Engineers running Linux kernels that use the USB gadget core should check their versions; affected versions are not specified.