CVE-2023-54022: ALSA: usb-audio: Fix potential memory leaks at error path for UMP open
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Fix potential memory leaks at error path for UMP open
The allocation and initialization errors at alloc_midi_urbs() that is
called at MIDI 2.0 / UMP device are supposed to be handled at the
caller side by invoking free_midi_urbs(). However, free_midi_urbs()
loops only for ep->num_urbs entries, and since ep->num_entries wasn't
updated yet at the allocation / init error in alloc_midi_urbs(), this
entry won't be released.
The intention of free_midi_urbs() is to release the whole elements, so
change the loop size to NUM_URBS to scan over all elements for fixing
the missed releases.
Also, the call of free_midi_urbs() is missing at
snd_usb_midi_v2_open(). Although it'll be released later at
reopen/close or disconnection, it's better to release immediately at
the error path.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the USB audio MIDI 2.0 UMP open path. If allocation or initialization fails, some allocated resources may not be freed immediately. The public bundle does not show active exploitation or a CVSS score.
Executive priority
Treat as routine patch management unless affected systems rely on USB audio or accept untrusted peripherals. The public evidence supports low urgency, but kernel fixes should still be applied through normal maintenance windows.
Technical view
The ALSA usb-audio driver’s UMP open error paths did not always call or fully execute free_midi_urbs(). The fix changes cleanup to scan NUM_URBS entries and adds missing cleanup in snd_usb_midi_v2_open(). Impact evidence is limited to kernel memory leakage on error paths.
Likely exposure
Exposure is most plausible on Linux systems running affected 6.5-era kernels with USB audio or MIDI 2.0 UMP devices. Typical servers are less exposed unless USB audio devices are attached or passed through.
Exploitation context
The source bundle does not identify exploitation in the wild, and KEV status is false. The described bug requires reaching specific USB audio UMP allocation or initialization error paths; no public weaponization details are provided.
Researcher notes
The affected data is limited and version notation is unclear in the bundle. Analysis should focus on snd-usb-audio UMP open cleanup behavior and whether downstream kernels backported f819b343aa95 or b1757fa30ef1.
Mitigation direction
Check the distribution kernel advisory for CVE-2023-54022.
Update to a kernel containing the referenced stable fixes.
Limit use of untrusted USB audio or MIDI peripherals until patched.
Monitor for ALSA usb-audio allocation or open errors.
Validation and detection
Inventory Linux kernel versions on systems with USB audio support.
Confirm vendor backports include the referenced stable commits.
Identify hosts using USB audio, MIDI, or UMP devices.
Review kernel logs for recurring ALSA usb-audio errors.
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.
cve · low confidence lookup
CVE-2023-54022 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.