CVE-2025-21859: USB: gadget: f_midi: f_midi_complete to call queue_work
In the Linux kernel, the following vulnerability has been resolved:
USB: gadget: f_midi: f_midi_complete to call queue_work
When using USB MIDI, a lock is attempted to be acquired twice through a
re-entrant call to f_midi_transmit, causing a deadlock.
Fix it by using queue_work() to schedule the inner f_midi_transmit() via
a high priority work queue from the completion handler.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21859 is a Linux kernel availability bug in the USB gadget MIDI function. When USB MIDI is used, the kernel can try to take the same lock twice and deadlock. The documented impact is denial of service, not data theft or code execution.
Executive priority
Schedule remediation through normal kernel or firmware maintenance, with higher priority for embedded, shared, or locally accessible devices using USB gadget MIDI. This is not supported as actively exploited in the provided sources, but it can affect availability.
Technical view
The flaw is CWE-667 in the Linux kernel USB gadget f_midi path. A completion handler can re-enter f_midi_transmit and attempt recursive lock acquisition, causing a deadlock. The kernel fix schedules the inner transmit through queue_work on a high-priority workqueue.
Likely exposure
Exposure appears narrow: Linux systems or embedded devices that enable and use the USB gadget MIDI function. General-purpose servers without USB gadget MIDI are less likely to be affected. Siemens and Debian references indicate downstream product and distribution relevance, but the bundle does not define all affected products.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, availability-only impact. The bundle does not report CISA KEV listing or active exploitation. Treat this as a local denial-of-service risk where USB gadget MIDI is reachable.
Researcher notes
The useful validation focus is configuration and reachability, not remote exposure. The bundle names the code path and fix strategy but does not provide complete downstream product coverage. Avoid assuming exploitability beyond local availability impact from the CVSS vector.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check Debian LTS and vendor advisories for packaged kernel updates.
For appliances, request vendor firmware guidance before changing kernels manually.
Disable unused USB gadget MIDI functionality where operationally safe.
Prioritize systems where local users or tenants can access gadget MIDI paths.
Validation and detection
Inventory Linux kernel versions across affected device classes.
Confirm whether USB gadget MIDI support is built, loaded, or configured.
Map running kernels against vendor fixed package or firmware advisories.
Review Debian LTS and device vendor notices for applicable versions.
Test remediation in representative devices before broad deployment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-667 · source CWE mapping
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.