CVE-2026-31723

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

usb: gadget: f_subset: 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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

usb: gadget: f_subset: Fix net_device lifecycle with device_move - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fde29916e4cc736c4ca6c78f331e12b2c73ccafd
generic

usb: gadget: f_subset: Fix net_device lifecycle with device_move - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9cbc4f109bb216623894d8819fb930210ed34b21
generic

usb: gadget: f_subset: Fix net_device lifecycle with device_move - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70707ce668494c4d35fe070dfbc7cc541b293107
generic

usb: gadget: f_subset: Fix net_device lifecycle with device_move - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06524cd1c9011bee141a87e43ab878641ed3652b

Vendor Advisories for CVE-2026-31723(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.81—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1—

All Vendor Advisories

(13)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 56× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 206 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-04 00:59 UTCOSV refresh
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 14:17 UTCEPSS rescore
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 13:44 UTCEG score recompute
  22. 2026-08-17 13:44 UTCVendor advisory
  23. 2026-08-17 13:44 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 05:18 UTCEG score recompute
Show 75 more
  1. 2026-08-16 05:18 UTCVendor advisory
  2. 2026-08-16 05:18 UTCGHSA enrichment
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 03:47 UTCEG score recompute
  6. 2026-08-14 03:47 UTCVendor advisory
  7. 2026-08-14 03:47 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-12 17:25 UTCEG score recompute
  10. 2026-08-12 17:25 UTCVendor advisory
  11. 2026-08-12 17:25 UTCGHSA enrichment
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-11 02:51 UTCEG score recompute
  14. 2026-08-11 02:51 UTCVendor advisory
  15. 2026-08-11 02:50 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 02:53 UTCEG score recompute
  18. 2026-08-10 02:53 UTCVendor advisory
  19. 2026-08-10 02:53 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 02:56 UTCEG score recompute
  22. 2026-08-09 02:56 UTCVendor advisory
  23. 2026-08-09 02:56 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 02:31 UTCEG score recompute
  26. 2026-08-08 02:31 UTCVendor advisory
  27. 2026-08-08 02:31 UTCGHSA enrichment
  28. 2026-08-07 02:34 UTCEG score recompute
  29. 2026-08-07 02:34 UTCVendor advisory
  30. 2026-08-07 02:34 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-05 22:36 UTCEG score recompute
  33. 2026-08-05 22:36 UTCVendor advisory
  34. 2026-08-05 22:36 UTCGHSA enrichment
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-03 20:24 UTCEG score recompute
  39. 2026-08-03 20:24 UTCVendor advisory
  40. 2026-08-03 20:24 UTCGHSA enrichment
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-02 05:40 UTCEG score recompute
  43. 2026-08-02 05:40 UTCVendor advisory
  44. 2026-08-02 05:40 UTCGHSA enrichment
  45. 2026-08-02 02:27 UTCEPSS rescore
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-28 15:36 UTCEPSS rescore
  50. 2026-07-26 14:54 UTCEPSS rescore
  51. 2026-07-26 14:54 UTCEPSS rescore
  52. 2026-07-25 14:18 UTCEPSS rescore
  53. 2026-07-25 14:17 UTCEPSS rescore
  54. 2026-07-24 14:17 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:08 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-22 14:08 UTCEPSS rescore
  60. 2026-07-21 15:24 UTCEPSS rescore
  61. 2026-07-21 15:24 UTCEPSS rescore
  62. 2026-07-20 17:08 UTCEPSS rescore
  63. 2026-07-20 17:08 UTCEPSS rescore
  64. 2026-07-19 19:18 UTCOSV refresh
  65. 2026-07-19 14:31 UTCEPSS rescore
  66. 2026-07-19 14:31 UTCEPSS rescore
  67. 2026-07-19 02:29 UTCEPSS rescore
  68. 2026-07-18 10:04 UTCEPSS rescore
  69. 2026-07-18 10:04 UTCEPSS rescore
  70. 2026-07-16 17:03 UTCEPSS rescore
  71. 2026-07-16 17:03 UTCEPSS rescore
  72. 2026-07-15 16:57 UTCEPSS rescore
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 02:00 UTCEPSS rescore
  75. 2026-07-15 02:00 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2026-31723?
CVE-2026-31723 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: fsubset: Fix netdevice 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…
When was CVE-2026-31723 disclosed?
CVE-2026-31723 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31723 actively exploited?
CVE-2026-31723 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31723?
CVE-2026-31723 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31723, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31723

Explore →

Is Your Infrastructure Affected by CVE-2026-31723?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs