Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 14730506b9e2a09d10c963a57a72ed528482fc15, 2479c26019a4009d84c7b98031a9fd7f9871a16b, 4ccdccff8febc5456aff684627f9a4c5c83b9346.

Low priority for now. Upgrade to Linux Linux 14730506b9e2a09d10c963a57a72ed528482fc15, 2479c26019a4009d84c7b98031a9fd7f9871a16b, 4ccdccff8febc5456aff684627f9a4c5c83b9346 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 1, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31724

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.11affected
    • b29002a157940752dfed2c488b2011f63f007d71 and later · before 2479c26019a4009d84c7b98031a9fd7f9871a16baffected · git
    • b29002a157940752dfed2c488b2011f63f007d71 and later · before b1d854462510f7b7c504bfd5f8ec19c0737ed5e4affected · git
    • b29002a157940752dfed2c488b2011f63f007d71 and later · before a6b8bce01a30a8c05c034bbc36c34845d65d644faffected · git
    • b29002a157940752dfed2c488b2011f63f007d71 and later · before 4ccdccff8febc5456aff684627f9a4c5c83b9346affected · git
    • b29002a157940752dfed2c488b2011f63f007d71 and later · before 14730506b9e2a09d10c963a57a72ed528482fc15affected · git
    • b29002a157940752dfed2c488b2011f63f007d71 and later · before d9270c9a8118c1535409db926ac1e2545dc97b81affected · git
    • before 3.11not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.11.1 and later · before 6.12.81
  • linux linux kernel6.13 and later · before 6.18.22
  • linux linux kernel6.19 and later · before 6.19.12
  • linux linux kernel7.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.12-16.19.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31722May 1, 2026 · usb: gadget: f_rndis: Fix net_device lifecycle with device_move
    22Monitor
  • ← EarlierCVE-2026-31723May 1, 2026 · usb: gadget: f_subset: Fix net_device lifecycle with device_move
    22Monitor
  • Later →CVE-2026-31725May 1, 2026 · usb: gadget: f_ecm: Fix net_device lifecycle with device_move
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux14730506b9e2a09d10c963a57a72ed528482fc15Vendor (CNA)
Linux Linux2479c26019a4009d84c7b98031a9fd7f9871a16bVendor (CNA)
Linux Linux4ccdccff8febc5456aff684627f9a4c5c83b9346Vendor (CNA)
Linux Linuxa6b8bce01a30a8c05c034bbc36c34845d65d644fVendor (CNA)
Linux Linuxb1d854462510f7b7c504bfd5f8ec19c0737ed5e4Vendor (CNA)
Linux Linuxd9270c9a8118c1535409db926ac1e2545dc97b81Vendor (CNA)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records