CVE-2026-64584usb: gadget: f_midi: cancel pending IN work before freeing the midi object
- 7.8HighCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 18 days later
· 18 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 3635523e9b96213969693c320302d536774d8e9b – < f3c6f2c38062703d3dc7f86958bb0790c6959add
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < df18150126f66817e4d3f79f309e9c92d6ff384e
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < 620955b222c47332297d6bf38f78541aa699238a
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < 380b4bef46c2eb260c7a9c6bb2c5be33ce5a38f9
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < 87bc316dd6fc90072297c635e10b9aa6075ecda1
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < f45089eaad0a083d71d84ff175741d7e157d9b69
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < ac9a51d910bb7465c554c45320cb6c09f3d0b49d
- affected 8653d71ce3763aedcf3d2331f59beda3fecd79e4 – < 5650c18d93a1db7e27cb5a40b394747eb4686d5b
- affected 89019ab7a64fcdf98a2ba7799e5c6aff58d4a05d
- affected 5.10.235 – < 5.10.265
- affected 5.4.291 – < 5.5
- affected 5.12
- unaffected < 5.12
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/f3c6f2c38062703d3dc7f86958bb0790c6959add (opens in a new tab)
- https://git.kernel.org/stable/c/df18150126f66817e4d3f79f309e9c92d6ff384e (opens in a new tab)
- https://git.kernel.org/stable/c/620955b222c47332297d6bf38f78541aa699238a (opens in a new tab)
- https://git.kernel.org/stable/c/380b4bef46c2eb260c7a9c6bb2c5be33ce5a38f9 (opens in a new tab)
- https://git.kernel.org/stable/c/87bc316dd6fc90072297c635e10b9aa6075ecda1 (opens in a new tab)
- https://git.kernel.org/stable/c/f45089eaad0a083d71d84ff175741d7e157d9b69 (opens in a new tab)
- https://git.kernel.org/stable/c/ac9a51d910bb7465c554c45320cb6c09f3d0b49d (opens in a new tab)
- https://git.kernel.org/stable/c/5650c18d93a1db7e27cb5a40b394747eb4686d5b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-53771 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64584)Record last updated .