linux — security advisory
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.
- Products
- linux
- Affected versions
- 6.1.27-1, 6.1.37-1, 6.1.38-1, 6.1.38-2, 6.1.38-2~bpo11+1, 6.1.38-3, 6.1.38-4, 6.1.38-4~bpo11+1, 6.1.52-1, 6.1.55-1, 6.1.55-1~bpo11+1, 6.1.64-1, 6.1.66-1, 6.1.67-1, 6.1.69-1, 6.1.69-1~bpo11+1, 6.1.76-1, 6.1.76-1~bpo11+1, 6.1.82-1, 6.1.85-1, 6.1.90-1, 6.1.90-1~bpo11+1, 6.1.94-1, 6.1.94-1~bpo11+1, 6.1.98-1
- Fixed versions
- 6.1.99-1, 6.8.11-1
- CVEs
- CVE-2024-36894
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 16:19 UTC · Revision 1
Source evidence
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.
osv:DEBIAN-CVE-2024-36894
linux
Fixed versions: 6.1.99-1
linux
Fixed versions: 6.8.11-1
linux
Fixed versions: 6.8.11-1
Complete source record
{
"id": "2b8498ec1c6290cc40c9bfad7cf10d0a2324646a8386ca30ce6bd905c426727c",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2024-36894",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2024-36894",
"summary": "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. ",
"evidence": "osv:DEBIAN-CVE-2024-36894",
"products": [
{
"name": {
"value": "linux",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.99-1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "6.1.27-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.37-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-2",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-2~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-3",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-4",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-4~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.52-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.55-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.55-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.64-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.66-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.67-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.69-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.69-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.76-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.76-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.82-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.85-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.90-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.90-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.94-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.94-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.98-1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "linux",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.8.11-1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "linux",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.8.11-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2024-36894",
"aliases": [
"DEBIAN-CVE-2024-36894"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.1.99-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"6.1.27-1",
"6.1.37-1",
"6.1.38-1",
"6.1.38-2",
"6.1.38-2~bpo11+1",
"6.1.38-3",
"6.1.38-4",
"6.1.38-4~bpo11+1",
"6.1.52-1",
"6.1.55-1",
"6.1.55-1~bpo11+1",
"6.1.64-1",
"6.1.66-1",
"6.1.67-1",
"6.1.69-1",
"6.1.69-1~bpo11+1",
"6.1.76-1",
"6.1.76-1~bpo11+1",
"6.1.82-1",
"6.1.85-1",
"6.1.90-1",
"6.1.90-1~bpo11+1",
"6.1.94-1",
"6.1.94-1~bpo11+1",
"6.1.98-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-36894.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.11-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-36894.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.11-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-36894.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-15T09:47:29.085513812Z",
"provider": "osv",
"upstream": [
"CVE-2024-36894"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2024-36894"
]
},
"related_cves": [
{
"value": "CVE-2024-36894",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 327466,
"published_at": "2024-05-30T16:15:12.857+00:00"
}