Answer in brief
CVE-2024-36894 records a Unknown severity vulnerability in usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-36894 records a Unknown severity vulnerability in usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <f71a53148ce34898fef099b75386a3a9f4449311 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <9e72ef59cbe61cd1243857a6418ca92104275867 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <e500b1c4e29ad0bd1c1332a1eaea2913627a92dd || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <3613e5023f09b3308545e9d1acda86017ebd418a || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <73c05ad46bb4fbbdb346004651576d1c8dbcffbb || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <d7461830823242702f5d84084bcccb25159003f4 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <24729b307eefcd7c476065cd7351c1a018082c19 | f71a53148ce34898fef099b75386a3a9f4449311, 9e72ef59cbe61cd1243857a6418ca92104275867, e500b1c4e29ad0bd1c1332a1eaea2913627a92dd, 3613e5023f09b3308545e9d1acda86017ebd418a, a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14, 73c05ad46bb4fbbdb346004651576d1c8dbcffbb, d7461830823242702f5d84084bcccb25159003f4, 24729b307eefcd7c476065cd7351c1a018082c19 |
| Linux/Linuxgeneric | 3.15 | Not reported |
| linux/linux_kernelgeneric | >=2e4c7553cd6f <73c05ad46bb4 | 73c05ad46bb4 |
| linux/linux_kernelgeneric | >=2e4c7553cd6f <d74618308232 | d74618308232 |
| linux/linux_kernelgeneric | >=2e4c7553cd6f <24729b307eef || >=2e4c7553cd6f <f71a53148ce3 || >=2e4c7553cd6f <9e72ef59cbe6 || >=2e4c7553cd6f <e500b1c4e29a || >=2e4c7553cd6f <3613e5023f09 || >=2e4c7553cd6f <a0fdccb1c9e0 || 3.15 | 24729b307eef, f71a53148ce3, 9e72ef59cbe6, e500b1c4e29a, 3613e5023f09, a0fdccb1c9e0 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
May 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. There is a scenario where the FFS application issues an AIO cancel call, while the UDC is handling a soft disconnect. For a DWC3 based implementation, the callstack looks like the following: DWC3 Gadget FFS Application dwc3_gadget_soft_disconnect() ... --> dwc3_stop_active_transfers() --> dwc3_gadget_giveback(-ESHUTDOWN) --> ffs_epfile_async_io_complete() ffs_aio_cancel() --> usb_ep_free_request() --> usb_ep_dequeue() There is currently no locking implemented between the AIO completion handler and AIO cancel, so the issue occurs if the completion routine is running in parallel to an AIO cancel call coming from the FFS application. As the completion call frees the USB request (io_data->req) the FFS application is also referencing it for the usb_ep_dequeue() call. This can lead to accessing a stale/hanging pointer. commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently") relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can't be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a USB request) will call the function driver's completion handler in the same context. Hence, leading into a deadlock. Fix this issue by moving the usb_ep_free_request() back to ffs_user_copy_worker(), and ensuring that it explicitly sets io_data->req to NULL after freeing it within the ffs->eps_lock. This resolves the race condition above, as the ffs_aio_cancel() routine will not continue attempting to dequeue a request that has already been freed, or the ffs_user_copy_work() not freeing the USB request until the AIO cancel is done referencing it. This fix depends on commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently")
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <f71a53148ce34898fef099b75386a3a9f4449311 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <9e72ef59cbe61cd1243857a6418ca92104275867 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <e500b1c4e29ad0bd1c1332a1eaea2913627a92dd || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <3613e5023f09b3308545e9d1acda86017ebd418a || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <73c05ad46bb4fbbdb346004651576d1c8dbcffbb || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <d7461830823242702f5d84084bcccb25159003f4 || >=2e4c7553cd6f9c68bb741582dcb614edcbeca70f <24729b307eefcd7c476065cd7351c1a018082c19 | f71a53148ce34898fef099b75386a3a9f4449311, 9e72ef59cbe61cd1243857a6418ca92104275867, e500b1c4e29ad0bd1c1332a1eaea2913627a92dd, 3613e5023f09b3308545e9d1acda86017ebd418a, a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14, 73c05ad46bb4fbbdb346004651576d1c8dbcffbb, d7461830823242702f5d84084bcccb25159003f4, 24729b307eefcd7c476065cd7351c1a018082c19 |
| Linux/Linuxgeneric | 3.15 | Not reported |
| linux/linux_kernelgeneric | >=2e4c7553cd6f <73c05ad46bb4 | 73c05ad46bb4 |
| linux/linux_kernelgeneric | >=2e4c7553cd6f <d74618308232 | d74618308232 |
| linux/linux_kernelgeneric | >=2e4c7553cd6f <24729b307eef || >=2e4c7553cd6f <f71a53148ce3 || >=2e4c7553cd6f <9e72ef59cbe6 || >=2e4c7553cd6f <e500b1c4e29a || >=2e4c7553cd6f <3613e5023f09 || >=2e4c7553cd6f <a0fdccb1c9e0 || 3.15 | 24729b307eef, f71a53148ce3, 9e72ef59cbe6, e500b1c4e29a, 3613e5023f09, a0fdccb1c9e0 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
May 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete FFS based applications can utilize the aio_cancel() callback to dequeue pending USB requests submitted to the UDC. There is a scenario where the FFS application issues an AIO cancel call, while the UDC is handling a soft disconnect. For a DWC3 based implementation, the callstack looks like the following: DWC3 Gadget FFS Application dwc3_gadget_soft_disconnect() ... --> dwc3_stop_active_transfers() --> dwc3_gadget_giveback(-ESHUTDOWN) --> ffs_epfile_async_io_complete() ffs_aio_cancel() --> usb_ep_free_request() --> usb_ep_dequeue() There is currently no locking implemented between the AIO completion handler and AIO cancel, so the issue occurs if the completion routine is running in parallel to an AIO cancel call coming from the FFS application. As the completion call frees the USB request (io_data->req) the FFS application is also referencing it for the usb_ep_dequeue() call. This can lead to accessing a stale/hanging pointer. commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently") relocated the usb_ep_free_request() into ffs_epfile_async_io_complete(). However, in order to properly implement locking to mitigate this issue, the spinlock can't be added to ffs_epfile_async_io_complete(), as usb_ep_dequeue() (if successfully dequeuing a USB request) will call the function driver's completion handler in the same context. Hence, leading into a deadlock. Fix this issue by moving the usb_ep_free_request() back to ffs_user_copy_worker(), and ensuring that it explicitly sets io_data->req to NULL after freeing it within the ffs->eps_lock. This resolves the race condition above, as the ffs_aio_cancel() routine will not continue attempting to dequeue a request that has already been freed, or the ffs_user_copy_work() not freeing the USB request until the AIO cancel is done referencing it. This fix depends on commit b566d38857fc ("usb: gadget: f_fs: use io_data->status consistently")
Quoted source text, attributed separately from HOL analysis.