CVE-2026-31756: usb: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop()
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.09% (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 4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4, 5.15.203, 51b62286fc668c6eb74dee7624ec0beec3c5a0ed.
Low priority for now. Upgrade to Linux Linux 4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4, 5.15.203, 51b62286fc668c6eb74dee7624ec0beec3c5a0ed 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: dwc2: gadget: Fix spin_lock/unlock mismatch in dwc2_hsotg_udc_stop() dwc2_gadget_exit_clock_gating() internally calls call_gadget() macro, which expects hsotg->lock to be held since it does spin_unlock/spin_lock around the gadget driver callback invocation. However, dwc2_hsotg_udc_stop() calls dwc2_gadget_exit_clock_gating() without holding the lock. This leads to: - spin_unlock on a lock that is not held (undefined behavior) - The lock remaining held after dwc2_gadget_exit_clock_gating() returns, causing a deadlock when spin_lock_irqsave() is called later in the same function. Fix this by acquiring hsotg->lock before calling dwc2_gadget_exit_clock_gating() and releasing it afterwards, which satisfies the locking requirement of the call_gadget() macro.
- Published
- May 1, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-667
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.187 and later · before 5.15.203
- linux linux kernel6.1.143 and later · before 6.1.168
- linux linux kernel6.6.96 and later · before 6.6.134
- linux linux kernel6.12.36 and later · before 6.12.81
- linux linux kernel6.15.5 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
- b39c203690fa1678daecc60f347e43c8b593b969, 6.16affected
- 5cb3cb3db317c58d50b68f3ca3bb8343ea9d1acd and later · before e9fcca3e87463013d595c65c2189ffaa32ad3b50affected · git
- 1ac826cebc2776f91569f2aa9c9c3da2375d2096 and later · before 8ffe31acb3b77a30ae34d01719a269881569fb7faffected · git
- 41732f9febdccb4f9b87c13cb915d717d68ccafd and later · before beab10429439e20708036a66fb0d97ffb79da6a1affected · git
- ba78c2b3254c4a458c01776612e8a573e12f8d26 and later · before 4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4affected · git
- af076a41f8a28faf9ceb9dd2d88aef2c202ef39a and later · before 61937f686290494998236c680ce0836b8dd63a3faffected · git
- af076a41f8a28faf9ceb9dd2d88aef2c202ef39a and later · before 51b62286fc668c6eb74dee7624ec0beec3c5a0edaffected · git
- af076a41f8a28faf9ceb9dd2d88aef2c202ef39a and later · before 9bb4b5ed7f8c4f95cc556bdf042b0ba2fa13557aaffected · git
- 5.15.187 and later · before 5.15.203affected · semver
- 6.1.143 and later · before 6.1.168affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.12-1 | 6.19.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31754May 1, 2026 · usb: cdns3: gadget: fix state inconsistency on gadget init failure22Monitor
- ← EarlierCVE-2026-31755May 1, 2026 · usb: cdns3: gadget: fix NULL pointer dereference in ep_queue22Monitor
- Later →CVE-2026-31757May 1, 2026 · usb: misc: usbio: Fix URB memory leak on submit failure22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4 | Vendor (CNA) |
| Linux Linux | 5.15.203 | Vendor (CNA) |
| Linux Linux | 51b62286fc668c6eb74dee7624ec0beec3c5a0ed | Vendor (CNA) |
| Linux Linux | 6.1.168 | Vendor (CNA) |
| Linux Linux | 6.12.81 | Vendor (CNA) |
| Linux Linux | 6.16 | Vendor (CNA) |
| Linux Linux | 6.6.134 | Vendor (CNA) |
| Linux Linux | 61937f686290494998236c680ce0836b8dd63a3f | Vendor (CNA) |
| Linux Linux | 8ffe31acb3b77a30ae34d01719a269881569fb7f | Vendor (CNA) |
| Linux Linux | 9bb4b5ed7f8c4f95cc556bdf042b0ba2fa13557a | Vendor (CNA) |
| Linux Linux | beab10429439e20708036a66fb0d97ffb79da6a1 | Vendor (CNA) |
| Linux Linux | e9fcca3e87463013d595c65c2189ffaa32ad3b50 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package 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 researchersFinders, 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.
- 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)
CWE-667 · Improper LockingCVSS 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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/51b62286fc668c6eb74dee7624ec0beec3c5a0ed
- git.kernel.org/stable/c/61937f686290494998236c680ce0836b8dd63a3f
- git.kernel.org/stable/c/8ffe31acb3b77a30ae34d01719a269881569fb7f
- git.kernel.org/stable/c/9bb4b5ed7f8c4f95cc556bdf042b0ba2fa13557a
- git.kernel.org/stable/c/beab10429439e20708036a66fb0d97ffb79da6a1
- git.kernel.org/stable/c/e9fcca3e87463013d595c65c2189ffaa32ad3b50
Vendor advisories and official records. Exploit/PoC links are deliberately left out.