CVE-2024-57913: usb: gadget: f_fs: Remove WARN_ON in functionfs_bind
Noroxi assessment
Priority: Monitor (action score 18/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 19fc1c83454ca9d5699e39633ec79ce26355251c, 3e4d32cc145955d5c56c5498a3ff057e4aafa9d1, 82f60f3600aecd9ffcd0fbc4e193694511c85b47; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1.
Low priority for now. Upgrade to Linux Linux 19fc1c83454ca9d5699e39633ec79ce26355251c, 3e4d32cc145955d5c56c5498a3ff057e4aafa9d1, 82f60f3600aecd9ffcd0fbc4e193694511c85b47; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1 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: Remove WARN_ON in functionfs_bind This commit addresses an issue related to below kernel panic where panic_on_warn is enabled. It is caused by the unnecessary use of WARN_ON in functionsfs_bind, which easily leads to the following scenarios. 1.adb_write in adbd 2. UDC write via configfs ================= ===================== ->usb_ffs_open_thread() ->UDC write ->open_functionfs() ->configfs_write_iter() ->adb_open() ->gadget_dev_desc_UDC_store() ->adb_write() ->usb_gadget_register_driver_owner ->driver_register() ->StartMonitor() ->bus_add_driver() ->adb_read() ->gadget_bind_driver() <times-out without BIND event> ->configfs_composite_bind() ->usb_add_function() ->open_functionfs() ->ffs_func_bind() ->adb_open() ->functionfs_bind() <ffs->state !=FFS_ACTIVE> The adb_open, adb_read, and adb_write operations are invoked from the daemon, but trying to bind the function is a process that is invoked by UDC write through configfs, which opens up the possibility of a race condition between the two paths. In this race scenario, the kernel panic occurs due to the WARN_ON from functionfs_bind when panic_on_warn is enabled. This commit fixes the kernel panic by removing the unnecessary WARN_ON. Kernel panic - not syncing: kernel: panic_on_warn set ... [ 14.542395] Call trace: [ 14.542464] ffs_func_bind+0x1c8/0x14a8 [ 14.542468] usb_add_function+0xcc/0x1f0 [ 14.542473] configfs_composite_bind+0x468/0x588 [ 14.542478] gadget_bind_driver+0x108/0x27c [ 14.542483] really_probe+0x190/0x374 [ 14.542488] __driver_probe_device+0xa0/0x12c [ 14.542492] driver_probe_device+0x3c/0x220 [ 14.542498] __driver_attach+0x11c/0x1fc [ 14.542502] bus_for_each_dev+0x104/0x160 [ 14.542506] driver_attach+0x24/0x34 [ 14.542510] bus_add_driver+0x154/0x270 [ 14.542514] driver_register+0x68/0x104 [ 14.542518] usb_gadget_register_driver_owner+0x48/0xf4 [ 14.542523] gadget_dev_desc_UDC_store+0xf8/0x144 [ 14.542526] configfs_write_iter+0xf0/0x138
- Published
- Jan 19, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-362
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 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
- 4.7
- CNA · Linux
- 4.7
- agree
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.35 and later · before 5.4.290
- linux linux kernel5.5 and later · before 5.10.234
- linux linux kernel5.11 and later · before 5.15.177
- linux linux kernel5.16 and later · before 6.1.125
- linux linux kernel6.2 and later · before 6.6.72
- linux linux kernel6.7 and later · before 6.12.10
- linux linux kernel6.13
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
- 2.6.35affected
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before bfe60030fcd976e3546e1f73d6d0eb3fea26442eaffected · git
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before 3e4d32cc145955d5c56c5498a3ff057e4aafa9d1affected · git
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before 19fc1c83454ca9d5699e39633ec79ce26355251caffected · git
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before 82f60f3600aecd9ffcd0fbc4e193694511c85b47affected · git
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before ea6a1498742430eb2effce0d1439ff29ef37dd7daffected · git
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before a8b6a18b9b66cc4c016d63132b59ce5383f7cdd2affected · git
- ddf8abd2599491cbad959c700b90ba72a5dce8d0 and later · before dfc51e48bca475bbee984e90f33fdc537ce09699affected · git
- before 2.6.35not affected · semver
- 5.4.290 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.128-1 | 6.1.128-1 |
| Debian:13 | linux | before 6.12.10-1 | 6.12.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-21650Jan 19, 2025 · net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue31Monitor
- ← EarlierCVE-2025-21651Jan 19, 2025 · net: hns3: don't auto enable misc vector18Monitor
- Later →CVE-2024-57917Jan 19, 2025 · topology: Keep the cpumask unchanged when printing cpumap31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 19fc1c83454ca9d5699e39633ec79ce26355251c | Vendor (CNA) |
| Linux Linux | 3e4d32cc145955d5c56c5498a3ff057e4aafa9d1 | Vendor (CNA) |
| Linux Linux | 82f60f3600aecd9ffcd0fbc4e193694511c85b47 | Vendor (CNA) |
| Linux Linux | a8b6a18b9b66cc4c016d63132b59ce5383f7cdd2 | Vendor (CNA) |
| Linux Linux | bfe60030fcd976e3546e1f73d6d0eb3fea26442e | Vendor (CNA) |
| Linux Linux | dfc51e48bca475bbee984e90f33fdc537ce09699 | Vendor (CNA) |
| Linux Linux | ea6a1498742430eb2effce0d1439ff29ef37dd7d | Vendor (CNA) |
| azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 | 6.6.78.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.128-1 · Debian:12 | Package 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 researchersFinders, 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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- 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:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/3e4d32cc145955d5c56c5498a3ff057e4aafa9d1
- git.kernel.org/stable/c/82f60f3600aecd9ffcd0fbc4e193694511c85b47
- git.kernel.org/stable/c/a8b6a18b9b66cc4c016d63132b59ce5383f7cdd2
- git.kernel.org/stable/c/bfe60030fcd976e3546e1f73d6d0eb3fea26442e
- git.kernel.org/stable/c/dfc51e48bca475bbee984e90f33fdc537ce09699
- git.kernel.org/stable/c/ea6a1498742430eb2effce0d1439ff29ef37dd7d
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.