CVE-2025-40093: usb: gadget: f_ecm: Refactor bind path to use __free()
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: f_ecm: Refactor bind path to use __free()
After an bind/unbind cycle, the ecm->notify_req is left stale. If a
subsequent bind fails, the unified error label attempts to free this
stale request, leading to a NULL pointer dereference when accessing
ep->ops->free_request.
Refactor the error handling in the bind path to use the __free()
automatic cleanup mechanism.
Security readout for executives and security teams
Plain-English summary
A Linux USB gadget networking flaw can crash the kernel during specific device reconfiguration failures. Systems using the Ethernet Control Model gadget function are the likely concern. The supplied record rates it 7.8 High, but the documented mechanism establishes a denial-of-service condition more clearly than data theft or code execution.
Executive priority
Prioritize embedded devices, appliances, and systems intentionally operating as USB network gadgets. Treat confirmed exposed systems as high-priority patching candidates because a local actor may trigger a kernel failure. General Linux servers without USB gadget ECM use are less likely to be exposed.
Technical view
After an f_ecm bind/unbind cycle, ecm->notify_req can remain stale. If a later bind fails, shared cleanup attempts to free that request and dereferences ep->ops->free_request through a NULL pointer. Linux resolved the error path by using automatic __free() cleanup.
Likely exposure
Exposure appears limited to Linux systems that build or use the USB gadget f_ecm function and encounter the required bind, unbind, and failed rebinding sequence. The supplied affected-version data is broad and contains ambiguous entries, so kernel commit ancestry or distributor guidance should determine exposure.
Exploitation context
The CVSS vector describes local, low-privilege, low-complexity access without user interaction. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. It also does not establish remote network exploitation.
Researcher notes
The documented primitive is stale-request cleanup followed by a NULL pointer dereference. Although CVSS claims high confidentiality, integrity, and availability impacts, the supplied technical description directly substantiates a crash path; it does not explain data disclosure, privilege escalation, or code execution. Exact version-to-fix mapping requires commit or vendor analysis.
Mitigation direction
Update to a vendor-supported kernel containing the applicable Linux stable correction.
Check distributor guidance for the fixed package corresponding to your kernel branch.
Restrict untrusted local access where prompt kernel updates are not possible.
Disable unused USB gadget ECM functionality if operationally safe and vendor-supported.
Validation and detection
Inventory kernel versions and identify devices using USB gadget ECM functionality.
Compare kernel commit ancestry against the five referenced Linux stable corrections.
Confirm fixed package status through the operating-system or appliance vendor.
Review kernel crash records for f_ecm cleanup or free_request NULL dereferences.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-40093 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.