Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

EPSS 0.01% · P2
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-36894

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
usb: gadget: f_fs: Fix race between aio_cancel() and AIO request complete
Source: NVD (National Vulnerability Database)
Vulnerability 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")
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于 usb:gadget:f_fs 模块存在竞争条件漏洞。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 2e4c7553cd6f9c68bb741582dcb614edcbeca70f ~ f71a53148ce34898fef099b75386a3a9f4449311 -
LinuxLinux 3.15 -

II. Public POCs for CVE-2024-36894

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-36894

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-05-30 · 93 CVEs total

CVE-2024-36927ipv4: Fix uninit-value access in __ip_make_skb()
CVE-2024-36922wifi: iwlwifi: read txq->read_ptr under lock
CVE-2024-36920scsi: mpi3mr: Avoid memcpy field-spanning write WARNING
CVE-2024-36916blk-iocost: avoid out of bounds shift
CVE-2024-36917block: fix overflow in blk_ioctl_discard()
CVE-2024-36914drm/amd/display: Skip on writeback when it's not applicable
CVE-2024-36915nfc: llcp: fix nfc_llcp_setsockopt() unsafe copies
CVE-2024-36913Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails
CVE-2024-36919scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload
CVE-2024-36925swiotlb: initialise restricted pool list_head when SWIOTLB_DYNAMIC=y
CVE-2024-36924scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up()
CVE-2024-36926powerpc/pseries/iommu: LPAR panics during boot up with a frozen PE
CVE-2024-36928s390/qeth: Fix kernel panic after setting hsuid
CVE-2024-36929net: core: reject skb_copy(_expand) for fraglist GSO skbs
CVE-2024-36930spi: fix null pointer dereference within spi_sync
CVE-2024-36932thermal/debugfs: Prevent use-after-free from occurring after cdev removal
CVE-2024-36931s390/cio: Ensure the copied buf is NUL terminated
CVE-2024-36933nsh: Restore skb->{protocol,data,mac_header} for outer header in nsh_gso_segment().
CVE-2024-36934bna: ensure the copied buf is NUL terminated
CVE-2024-36935ice: ensure the copied buf is NUL terminated

Showing top 20 of 93 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-36894

No comments yet


Leave a comment