# CVE-2026-64584: linux: In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_midi: cancel pending IN work befo...

CVE-2026-64584 is fixed in 17 products on 1 platform, first by DEBIAN-CVE-2026-64584, released August 7, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-64584
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0012
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 6, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_midi: cancel pending IN work before freeing the midi object  The f_midi driver embeds a work item (midi->work) whose handler, f_midi_in_work(), dereferences the enclosing struct f_midi through container_of().  This work is armed from two sites: f_midi_complete(), on a normal IN-endpoint completion, and f_midi_in_trigger(), on an ALSA rawmidi output-stream start.  Neither f_midi_disable() nor f_midi_unbind() cancels midi->work. f_midi_disable() only disables the endpoints and drains the in_req_fifo; it does not synchronize the work item, and the sound card is released asynchronously to the final free of the midi object.  The midi object is reference-counted (midi->free_ref) and is freed in f_midi_free() only once both the usb_function reference and the rawmidi private_data reference have been dropped.  In f_midi_unbind(), f_midi_disable() runs before the sound card is released, so while the USB endpoints are already disabled the rawmidi device is still usable by an open substream.  A concurrent userspace write on such a substream can reach f_midi_in_trigger() and queue midi->work again after f_midi_disable() has returned.  A work item armed this way may still be pending when the last reference drops and f_midi_free() proceeds to kfree(midi), letting f_midi_in_work() dereference the struct after it has been freed, a use-after-free.  For this reason cancelling midi->work in f_midi_disable() would not be sufficient: the ALSA trigger path can rearm the work after disable() returns.  Cancelling at the refcount-zero free site is the boundary after which neither arming source can survive, because by then both references that keep the midi object alive have been dropped: the USB endpoints are already disabled and the rawmidi device has been released.  Fix this by calling cancel_work_sync(&midi->work) in the refcount-zero block of f_midi_free(), before the embedded work_struct is freed along with the rest of the structure.  opts->lock is a sleeping mutex, so calling cancel_work_sync() under it is permitted, and the handler takes midi->transmit_lock rather than opts->lock, so no self-deadlock can occur while it waits for a running instance of the work to finish.  This issue was found by an in-house static analysis tool.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-64kb sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-azure sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-default sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-default sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.38.1.160000.2.22 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.81.1.150700.17.45.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-default-base sles 16.0 | 6.12.0-160000.38.1.160000.2.23 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-docs sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-livepatch-SLE15-SP7-RT_Update_20 sles 15.7 | 1-150700.1.3.1 | [SUSE-SU-2026:4120-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4120-1.md) | Sep 10, 2026 |
| Linux | kernel-livepatch-SLE15-SP7_Update_21 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-source sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-source sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-syms sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 |
| Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.81.1 | [SUSE-SU-2026:4254-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4254-1.md) | Oct 7, 2026 |
| Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 |
| Linux | linux Debian 12.15 (bookworm) | 6.1.187-1 | [DEBIAN-CVE-2026-64584](https://patchblox.com/security/data/fix/linux/debian-cve-2026-64584.md) | Aug 7, 2026 |
| Linux | linux Debian 13.5 (trixie) | 6.12.101-1 | [DEBIAN-CVE-2026-64584](https://patchblox.com/security/data/fix/linux/debian-cve-2026-64584.md) | Aug 7, 2026 |
| Linux | linux Debian 14 | 7.1.6-1 | [DEBIAN-CVE-2026-64584](https://patchblox.com/security/data/fix/linux/debian-cve-2026-64584.md) | Aug 7, 2026 |
| Linux | linux-6.12 Debian 12.15 (bookworm) | 6.12.101-1~deb12u1 | [DEBIAN-CVE-2026-64584](https://patchblox.com/security/data/fix/linux/debian-cve-2026-64584.md) | Aug 7, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

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.
