usb: core: hcd: fix possible deadlock in rh control transfers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e57e780b346a7277fdd3bde765d9d8728b99bfa1 · < 549672a3fb6b36ea408238f89ecf9f41d2da6225| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: core: hcd: fix possible deadlock in rh control transfers
>From within the SCSI error handler memory allocations must not trigger IO. Handling errors in UAS and the storage driver may involve resetting a device. The thread doing the reset itself relies on VM magic. However, that is insufficient, as resetting a device involves resuming it. Resumption as well as resetting involves conrol transfers to the parent of the device to be reset. That may be a root hub. Hence usbcore must heed the flags passed to usb_submit_urb() processing control transfers to root hubs.
The problem exist since the storage driver has been merged.
From the CVE record · Linux
Linux kernel USB core may deadlock during root hub control transfers when a storage error handler resets a device. The input does not describe an attacker-controlled trigger or specify whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with USB storage or UAS support should check their deployments; affected versions are not specified.