Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31756

5.5 · MEDIUM

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…

Published May 1, 2026CWE-667EPSS 0.13%

Overview

CVE-2026-31756 is a medium-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/4ed9d2dd9f29828c311db6ec4b8e0d34bfd6d6a4Refgit.kernel.org/stable/c/51b62286fc668c6eb74dee7624ec0beec3c5a0edRefgit.kernel.org/stable/c/61937f686290494998236c680ce0836b8dd63a3fRefgit.kernel.org/stable/c/8ffe31acb3b77a30ae34d01719a269881569fb7fRefgit.kernel.org/stable/c/9bb4b5ed7f8c4f95cc556bdf042b0ba2fa13557aRefgit.kernel.org/stable/c/beab10429439e20708036a66fb0d97ffb79da6a1Refgit.kernel.org/stable/c/e9fcca3e87463013d595c65c2189ffaa32ad3b50

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31756?

CVE-2026-31756 is a medium-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-31756?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31756?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31756?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31756 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999