usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ddf8abd2599491cbad959c700b90ba72a5dce8d0 · < 6aee197b7fbcd61596a78b47d553f2f99111f217| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait
While performing fast composition switch, there is a possibility that the process of ffs_ep0_write/ffs_ep0_read get into a race condition due to ep0req being freed up from functionfs_unbind.
Consider the scenario that the ffs_ep0_write calls the ffs_ep0_queue_wait by taking a lock &ffs->ev.waitq.lock. However, the functionfs_unbind isn't bounded so it can go ahead and mark the ep0req to NULL, and since there is no NULL check in ffs_ep0_queue_wait we will end up in use-after-free.
Fix this by making a serialized execution between the two functions using a mutex_lock(ffs->mutex).
From the CVE record · Linux
A race between FunctionFS endpoint-zero reads or writes and unbinding can cause a use-after-free during a fast USB composition switch. The input does not specify the access or authentication an attacker would need to trigger it.
Engineers running Linux kernels that use USB FunctionFS should check whether their kernel includes the fix; affected versions were not specified.