CVE-2026-31728

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: 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: u_ether: Fix race between gether_disconnect and eth_stop

A race condition between gether_disconnect() and eth_stop() leads to a NULL pointer dereference. Specifically, if eth_stop() is triggered concurrently while gether_disconnect() is tearing down the endpoints, eth_stop() attempts to access the cleared endpoint descriptor, causing the following NPE:

Unable to handle kernel NULL pointer dereference Call trace: __dwc3_gadget_ep_enable+0x60/0x788 dwc3_gadget_ep_enable+0x70/0xe4 usb_ep_enable+0x60/0x15c eth_stop+0xb8/0x108

Because eth_stop() crashes while holding the dev->lock, the thread running gether_disconnect() fails to acquire the same lock and spins forever, resulting in a hardlockup:

Core - Debugging Information for Hardlockup core(7) Call trace: queued_spin_lock_slowpath+0x94/0x488 _raw_spin_lock+0x64/0x6c gether_disconnect+0x19c/0x1e8 ncm_set_alt+0x68/0x1a0 composite_setup+0x6a0/0xc50

The root cause is that the clearing of dev->port_usb in gether_disconnect() is delayed until the end of the function.

Move the clearing of dev->port_usb to the very beginning of gether_disconnect() while holding dev->lock. This cuts off the link immediately, ensuring eth_stop() will see dev->port_usb as NULL and safely bail out.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (8)

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ff689edfeceb5e3ec1623e09af2b2aa0f1098a8
generic

usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ad77458637b78ec655e3da5f112c862e6690a9d

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
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 (125 versions)6.19.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

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 5× in last 7d / 29× 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 197 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31728?
CVE-2026-31728 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uether: Fix race between getherdisconnect and eth_stop A race condition between getherdisconnect() and ethstop() leads to a NULL pointer dereference. Specifically, if eth_stop() is triggered concurrently while…
When was CVE-2026-31728 disclosed?
CVE-2026-31728 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-31728 actively exploited?
CVE-2026-31728 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 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31728?
CVE-2026-31728 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-31728?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31728, 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-31728

Explore →

Is Your Infrastructure Affected by CVE-2026-31728?

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

Start Free Scan →Browse All CVEs