CVE-2025-40093
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.
Affected versions
Linux kernel versions
2.6.27
and later are affected. Fixed in
6.1.158,
6.6.114,
6.12.55,
6.17.5,
6.18
and their respective stable series.
References
The following references provide additional information about CVE-2025-40093 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/070f341d86cf2c098d63e484a86c7c1d2696a868
-
PatchKernel patch commithttps://git.kernel.org/stable/c/15b9faf53ba8719700596e7ef78879ce200e8c2e
-
PatchKernel patch commithttps://git.kernel.org/stable/c/42988380ac67c76bb9dff8f77d7ef3eefd50b7b5
Frequently asked questions
-
What is CVE-2025-40093?
CVE-2025-40093 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 2.6.27 onward and has been patched in 6.1.158, 6.6.114, 6.12.55 and others. CVE-2025-40093 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2025-40093?
Yes — CVE-2025-40093 has been patched. Fixed versions include 6.1.158, 6.6.114, 6.12.55 and others. If you are running Linux kernel 2.6.27 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-40093 actively exploited?
No — CVE-2025-40093 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.