usb: gadget: f_hid: move list and spinlock inits from bind to alloc
CVE-2026-31721 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2026-31721, released May 15, 2026. It is not reported as exploited. Patch Radar priority: High.
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_hid: move list and spinlock inits from bind to alloc There was an issue when you did the following: - setup and bind an hid gadget - open /dev/hidg0 - use the resulting fd in EPOLL_CTL_ADD - unbind the UDC - bind the UDC - use the fd in EPOLL_CTL_DEL When CONFIG_DEBUG_LIST was enabled, a list_del corruption was reported within remove_wait_queue (via ep_remove_wait_queue). After some debugging I found out that the queues, which f_hid registers via poll_wait were the problem. These were initialized using init_waitqueue_head inside hidg_bind. So effectively, the bind function re-initialized the queues while there were still items in them. The solution is to move the initialization from hidg_bind to hidg_alloc to extend their lifetimes to the lifetime of the function instance. Additionally, I found many other possibly problematic init calls in the bind function, which I moved as well.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23237-1 | Aug 11, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.37.1.160000.2.19 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.37.1.160000.2.19 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.37.1 | OPENSUSE-SU-2026:21555-1 | Aug 12, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.37.1 | SUSE-SU-2026:23231-1 | Aug 11, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.170-1 | DEBIAN-CVE-2026-31721 | May 15, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.85-1 | DEBIAN-CVE-2026-31721 | May 15, 2026 |
| linux · Debian 14 | 6.19.12-1 | DEBIAN-CVE-2026-31721 | May 15, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.