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.
https://git.kernel.org/stable/c/e0e4f15d4225fb7156cc0e3c21eb8953114f9b89
https://git.kernel.org/stable/c/c4e232bd07fe2b69a6e5c380db41dd36b95e0524
https://git.kernel.org/stable/c/b399be2958456efe1b64b19c55a54a24e9035769
https://git.kernel.org/stable/c/642e04f5c292d04070ae6e4374fbf14cc40a2465
https://git.kernel.org/stable/c/5e5798880eb1533a7de6fb68eb14b2d8202ebf76
https://git.kernel.org/stable/c/48958478cb8dbc429a5b19f36e866b63d6297d1d
https://git.kernel.org/stable/c/010382937fb69892b3469ac4d30af072262f59e8