Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31728: usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop

Noroxi assessment

Priority: Monitor (action score 18/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.08% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 6ad77458637b78ec655e3da5f112c862e6690a9d, 8ff689edfeceb5e3ec1623e09af2b2aa0f1098a8, a259ba0bce3b192c04334499690372a250f7d0b1.

Low priority for now. Upgrade to Linux Linux 6ad77458637b78ec655e3da5f112c862e6690a9d, 8ff689edfeceb5e3ec1623e09af2b2aa0f1098a8, a259ba0bce3b192c04334499690372a250f7d0b1 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: 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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
May 1, 2026
Updated
Jun 17, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

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-31728

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

  • linux linux kernel2.6.27 and later · before 5.10.253
  • linux linux kernel5.11 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.169
  • linux linux kernel6.2 and later · before 6.6.134
  • linux linux kernel6.7 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

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

    • 2.6.27affected
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before f02980594deef751e42133714aee25228f1494c6affected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before e1e7a66584bf0aff3becb73c19fa31527889fc9eaffected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before a259ba0bce3b192c04334499690372a250f7d0b1affected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before f6813c2b2ae78def76b69e0f9d72f80e4a1c4acaaffected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before bbb09bb89ffa571475f66daca9482b974cd29d6aaffected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before 6ad77458637b78ec655e3da5f112c862e6690a9daffected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before 8ff689edfeceb5e3ec1623e09af2b2aa0f1098a8affected · git
    • 2b3d942c4878084a37991a65e66512c02b8fa2ad and later · before e1eabb072c75681f78312c484ccfffb7430f206eaffected · git
    • before 2.6.27not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
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-31726May 1, 2026 · usb: gadget: uvc: fix NULL pointer dereference during unbind race
    22Monitor
  • ← EarlierCVE-2026-31727May 1, 2026 · usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo
    22Monitor
  • Later →CVE-2026-31730May 1, 2026 · misc: fastrpc: possible double-free of cctx->remote_heap
    31Monitor

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 Linux6ad77458637b78ec655e3da5f112c862e6690a9dVendor (CNA)
Linux Linux8ff689edfeceb5e3ec1623e09af2b2aa0f1098a8Vendor (CNA)
Linux Linuxa259ba0bce3b192c04334499690372a250f7d0b1Vendor (CNA)
Linux Linuxbbb09bb89ffa571475f66daca9482b974cd29d6aVendor (CNA)
Linux Linuxe1e7a66584bf0aff3becb73c19fa31527889fc9eVendor (CNA)
Linux Linuxe1eabb072c75681f78312c484ccfffb7430f206eVendor (CNA)
Linux Linuxf02980594deef751e42133714aee25228f1494c6Vendor (CNA)
Linux Linuxf6813c2b2ae78def76b69e0f9d72f80e4a1c4acaVendor (CNA)
debian:linux6.1.170-1 · Debian:12Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.
  • Special conditions such as timing or configuration are required.

If successful

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

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

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

All records