Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-36894usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete

Description

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")

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-36894, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.6CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < f71a53148ce34898fef099b75386a3a9f4449311
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < 9e72ef59cbe61cd1243857a6418ca92104275867
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < e500b1c4e29ad0bd1c1332a1eaea2913627a92dd
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < 3613e5023f09b3308545e9d1acda86017ebd418a
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < 73c05ad46bb4fbbdb346004651576d1c8dbcffbb
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < d7461830823242702f5d84084bcccb25159003f4
    • affected 2e4c7553cd6f9c68bb741582dcb614edcbeca70f – < 24729b307eefcd7c476065cd7351c1a018082c19
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 4.19.317 – ≤ 4.19.*
    • unaffected 5.4.279 – ≤ 5.4.*
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.95 – ≤ 6.1.*
    • unaffected 6.6.31 – ≤ 6.6.*
    • unaffected 6.8.10 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-36894 badge
[![CVE-2024-36894](https://cveledger.app/badge/CVE-2024-36894.svg)](https://cveledger.app/cve/CVE-2024-36894)

Record last updated .