usb: mtu3: fix kernel panic at qmu transfer done irq handler
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 48e0d3735aa557a8adaf94632ca3cf78798e8505 · < 3a7d4959560a2ee493ef222e3b63d359365f41ec| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: mtu3: fix kernel panic at qmu transfer done irq handler
When handle qmu transfer irq, it will unlock @mtu->lock before give back request, if another thread handle disconnect event at the same time, and try to disable ep, it may lock @mtu->lock and free qmu ring, then qmu irq hanlder may get a NULL gpd, avoid the KE by checking gpd's value before handling it.
e.g. qmu done irq on cpu0 thread running on cpu1
qmu_done_tx() handle gpd [0] mtu3_requ_complete() mtu3_gadget_ep_disable() unlock @mtu->lock give back request lock @mtu->lock mtu3_ep_disable() mtu3_gpd_ring_free() unlock @mtu->lock lock @mtu->lock get next gpd [1]
[1]: goto [0] to handle next gpd, and next gpd may be NULL.
From the CVE record · Linux
The Linux kernel’s USB mtu3 QMU transfer-completion handler can encounter a NULL descriptor if an endpoint is disabled and its QMU ring is freed during interrupt handling. This race can cause a kernel panic; the input does not specify an attacker-controlled trigger, access requirements, or user interaction.
Engineers running Linux kernels with the USB mtu3 driver should check their kernel’s advisory; affected versions are not specified.