VulnerabilityPublished 1 May 2026Updated 21 Oct 2026

CVE-2026-31724: Linux kernel · usb: gadget: f_eem: Fix net_device lifecycle with device_move

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in d9270c9a8118c1535409db926ac1e2545dc97b81 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in d9270c9a8118c1535409db926ac1e2545dc97b81, b1d854462510f7b7c504bfd5f8ec19c0737ed5e4, a6b8bce01a30a8c05c034bbc36c34845d65d644f +2

Exploitation evidence

Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b29002a157940752dfed2c488b2011f63f007d71, < d9270c9a8118c1535409db926ac1e2545dc97b81	Fixed in d9270c9a8118c1535409db926ac1e2545dc97b81
LinuxLinux	Affected ≥ b29002a157940752dfed2c488b2011f63f007d71, < b1d854462510f7b7c504bfd5f8ec19c0737ed5e4	Fixed in b1d854462510f7b7c504bfd5f8ec19c0737ed5e4
LinuxLinux	Affected ≥ b29002a157940752dfed2c488b2011f63f007d71, < a6b8bce01a30a8c05c034bbc36c34845d65d644f	Fixed in a6b8bce01a30a8c05c034bbc36c34845d65d644f
LinuxLinux	Affected ≥ b29002a157940752dfed2c488b2011f63f007d71, < 14730506b9e2a09d10c963a57a72ed528482fc15	Fixed in 14730506b9e2a09d10c963a57a72ed528482fc15
LinuxLinux	Affected ≥ b29002a157940752dfed2c488b2011f63f007d71, < 4ccdccff8febc5456aff684627f9a4c5c83b9346	Fixed in 4ccdccff8febc5456aff684627f9a4c5c83b9346
LinuxLinux	Affected =3.11	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_eem: 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.

References

Community reviews

Loading reviews…