Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 24729b307eefcd7c476065cd7351c1a018082c19, 3613e5023f09b3308545e9d1acda86017ebd418a, 73c05ad46bb4fbbdb346004651576d1c8dbcffbb.

Low priority for now. Upgrade to Linux Linux 24729b307eefcd7c476065cd7351c1a018082c19, 3613e5023f09b3308545e9d1acda86017ebd418a, 73c05ad46bb4fbbdb346004651576d1c8dbcffbb or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 30, 2024
Updated
Oct 15, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-36894

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.15 and later · before 4.19.317
  • linux linux kernel4.20 and later · before 5.4.279
  • linux linux kernel5.5 and later · before 5.10.221
  • linux linux kernel5.11 and later · before 5.15.162
  • linux linux kernel5.16 and later · before 6.1.95
  • linux linux kernel6.2 and later · before 6.6.31
  • linux linux kernel6.7 and later · before 6.8.10
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.15affected
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before f71a53148ce34898fef099b75386a3a9f4449311affected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before 9e72ef59cbe61cd1243857a6418ca92104275867affected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before e500b1c4e29ad0bd1c1332a1eaea2913627a92ddaffected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before 3613e5023f09b3308545e9d1acda86017ebd418aaffected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before a0fdccb1c9e027e3195f947f61aa87d6d0d2ea14affected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before 73c05ad46bb4fbbdb346004651576d1c8dbcffbbaffected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before d7461830823242702f5d84084bcccb25159003f4affected · git
    • 2e4c7553cd6f9c68bb741582dcb614edcbeca70f and later · before 24729b307eefcd7c476065cd7351c1a018082c19affected · git
    • before 3.15not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linuxbefore 5.10.221-15.10.221-1
Debian:12linuxbefore 6.1.99-16.1.99-1
Debian:13linuxbefore 6.8.11-16.8.11-1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-64kbbefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-docsbefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-obs-buildbefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-sourcebefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSkernel-symsbefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1
SUSE:Linux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_28before 1-150400.9.3.11-150400.9.3.1
SUSE:Linux Enterprise Micro 5.3kernel-defaultbefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1
SUSE:Linux Enterprise Micro 5.3kernel-default-basebefore 5.14.21-150400.24.125.1.150400.24.60.15.14.21-150400.24.125.1.150400.24.60.1
SUSE:Linux Enterprise Micro 5.3kernel-rtbefore 5.14.21-150400.15.85.15.14.21-150400.15.85.1
SUSE:Linux Enterprise Micro 5.3kernel-source-rtbefore 5.14.21-150400.15.85.15.14.21-150400.15.85.1
SUSE:Linux Enterprise Server 15 SP4-LTSSkernel-zfcpdumpbefore 5.14.21-150400.24.125.15.14.21-150400.24.125.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-36020May 30, 2024 · i40e: fix vf may be used uninitialized in this function warning
    22Monitor
  • ← EarlierCVE-2024-36881May 30, 2024 · mm/userfaultfd: reset ptes when close() for wr-protected ones
    22Monitor
  • Later →CVE-2024-36899May 30, 2024 · gpiolib: cdev: Fix use after free in lineinfo_changed_notify
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux24729b307eefcd7c476065cd7351c1a018082c19Vendor (CNA)
Linux Linux3613e5023f09b3308545e9d1acda86017ebd418aVendor (CNA)
Linux Linux73c05ad46bb4fbbdb346004651576d1c8dbcffbbVendor (CNA)
Linux Linux9e72ef59cbe61cd1243857a6418ca92104275867Vendor (CNA)
Linux Linuxa0fdccb1c9e027e3195f947f61aa87d6d0d2ea14Vendor (CNA)
Linux Linuxd7461830823242702f5d84084bcccb25159003f4Vendor (CNA)
Linux Linuxe500b1c4e29ad0bd1c1332a1eaea2913627a92ddVendor (CNA)
Linux Linuxf71a53148ce34898fef099b75386a3a9f4449311Vendor (CNA)
debian:linux6.1.99-1 · Debian:12Package registry (OSV)
suse:kernel-64kb5.14.21-150400.24.125.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-default5.14.21-150400.24.125.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-default-base5.14.21-150400.24.125.1.150400.24.60.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-docs5.14.21-150400.24.125.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP4_Update_281-150400.9.3.1 · SUSE:Linux Enterprise Live Patching 15 SP4Package registry (OSV)
suse:kernel-obs-build5.14.21-150400.24.125.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-rt5.14.21-150400.15.85.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-source5.14.21-150400.24.125.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-source-rt5.14.21-150400.15.85.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:kernel-syms5.14.21-150400.24.125.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:kernel-zfcpdump5.14.21-150400.24.125.1 · SUSE:Linux Enterprise Server 15 SP4-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records