CVE-2026-64454None▾ SunlitIn the Linux kernel, the following vulnerability has been resolved: usb: dwc3: run gadget disconnect from sleepable suspend context dwc3_gadget_suspend() takes dwc->lock with IRQs disabled and then calls dwc3_disconnect_gadget(). For …
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc3: run gadget disconnect from sleepable suspend context
dwc3_gadget_suspend() takes dwc->lock with IRQs disabled and then calls dwc3_disconnect_gadget(). For async callbacks that helper only uses plain spin_unlock()/spin_lock(), so the gadget ->disconnect() callback still runs with IRQs disabled and any sleepable callback trips Lockdep.
This issue was found by our static analysis tool and then manually reviewed against the current tree.
The grounded PoC kept the dwc3_gadget_suspend() -> dwc3_disconnect_gadget() -> gadget_driver->disconnect() chain, and Lockdep reported:
BUG: sleeping function called from invalid context gadget_disconnect+0x21/0x39 [vuln_msv] dwc3_gadget_suspend.constprop.0+0x2b/0x42 [vuln_msv]
Keep the disconnect callback selection in one common helper, but add a sleepable suspend-side wrapper which snapshots the callback under dwc->lock and then runs it after spin_unlock_irqrestore(). The regular event path still uses the existing spin_unlock()/spin_lock() window.
Linux >= 20351ddb1f41cfb3ae20e105425ef43a28393d76 < b399be2958456efe1b64b19c55a54a24e9035769Linux >= ad43004fd5326bec4466ecc8a07fe0e570b553ca < 48958478cb8dbc429a5b19f36e866b63d6297d1dLinux >= c8540870af4ce6ddeb27a7bb5498b75fb29b643c < 5e5798880eb1533a7de6fb68eb14b2d8202ebf76Linux >= c8540870af4ce6ddeb27a7bb5498b75fb29b643c < e0e4f15d4225fb7156cc0e3c21eb8953114f9b89Linux >= c8540870af4ce6ddeb27a7bb5498b75fb29b643c < c4e232bd07fe2b69a6e5c380db41dd36b95e0524Linux >= c8540870af4ce6ddeb27a7bb5498b75fb29b643c < 642e04f5c292d04070ae6e4374fbf14cc40a2465Linux >= c8540870af4ce6ddeb27a7bb5498b75fb29b643c < 010382937fb69892b3469ac4d30af072262f59e8Linux 06684c72b6b153dc434bb6ccebbb49f4cd812b5eLinux >= 5.15.128 < 5.15.212Linux >= 6.1.30 < 6.1.178Linux >= 6.3.4 < 6.4Linux 6.4Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses