CVE-2026-31756
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-667
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.168
- Linux Kernel < 6.6.134
- Linux Kernel < 6.12.81
- Linux Kernel < 6.18.22
- Linux Kernel < 6.19.12
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-31756.md and follow it. Check whether this project is affected by CVE-2026-31756. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4
- https://git.kernel.org/stable/c/51b62286fc668c6eb74dee7624ec0beec3c5a0ed
- https://git.kernel.org/stable/c/61937f686290494998236c680ce0836b8dd63a3f
- https://git.kernel.org/stable/c/8ffe31acb3b77a30ae34d01719a269881569fb7f
- https://git.kernel.org/stable/c/9bb4b5ed7f8c4f95cc556bdf042b0ba2fa13557a
- https://git.kernel.org/stable/c/beab10429439e20708036a66fb0d97ffb79da6a1
- https://git.kernel.org/stable/c/e9fcca3e87463013d595c65c2189ffaa32ad3b50
References
- https://git.kernel.org/stable/c/4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4
- https://git.kernel.org/stable/c/51b62286fc668c6eb74dee7624ec0beec3c5a0ed
- https://git.kernel.org/stable/c/61937f686290494998236c680ce0836b8dd63a3f
- https://git.kernel.org/stable/c/8ffe31acb3b77a30ae34d01719a269881569fb7f
- https://git.kernel.org/stable/c/9bb4b5ed7f8c4f95cc556bdf042b0ba2fa13557a
- https://git.kernel.org/stable/c/beab10429439e20708036a66fb0d97ffb79da6a1
- https://git.kernel.org/stable/c/e9fcca3e87463013d595c65c2189ffaa32ad3b50