CVE-2026-99319

ALSA: usx2y: Refuse a retried DSP load after a failure

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

ALSA: usx2y: Refuse a retried DSP load after a failure

snd_usx2y_hwdep_dsp_load() sets up the asynchronous sequence URBs and
the interrupt URB when the FPGA firmware image with index 1 is loaded,
and then creates the ALSA devices. If usx2y_in04_init() or
usx2y_create_alsa_devices() fails, the URBs that were already set up
are left in place.

The core keeps the index unloaded when the callback fails, so user
space may issue the same request again. The second attempt then enters
usx2y_async_seq04_init() or usx2y_in04_init() with the URBs still
allocated and trips WARN_ON(usx2y->as04.buffer) or
WARN_ON(usx2y->in04_urb).

The URBs cannot be released at this point: the card may already have
registered PCM devices that user space can still open, and the
disconnect handler accesses the URBs without holding the DSP lock.
Mark the chip as hung instead, so that a retried request is refused
with -ENODEV and the assertions keep their meaning. The URBs are
released by snd_usx2y_card_private_free() when the card is freed.

A failing usx2y_async_seq04_init() still releases its own URBs, so that
path remains retryable.

Analysis

AI-generated

Technical impact

The vulnerability occurs when the ALSA usx2y driver fails to release USB Request Blocks that were allocated during a DSP firmware load and subsequently fails. The driver leaves those URBs in place and flags the device as hung, causing any retransmission of the load to be denied with –ENODEV. This leaves the audio hardware unusable and effectively denies service for applications that rely on that device. The underlying weakness is a resource‑management flaw that leaks kernel objects.

Affected Systems

The flaw affects the ALSA usx2y driver in the Linux kernel. It impacts any system whose kernel includes the usx2y module before the commits referenced in the advisory. Devices that use the usx2y hardware, such as certain USB audio interfaces that load DSP firmware via the driver, are affected.

Risk and Exploitability

The EPSS score is not provided and the vulnerability is not listed in the CISA KEV catalog, indicating no known active exploitation. The attack vector is local; an attacker must already have the ability to interact with the ALSA subsystem to trigger a DSP load failure and then retry. Remote exploitation is unlikely because the trigger requires direct interaction with the kernel driver. The risk is therefore moderate, with impact confined to environments that use the affected USB audio hardware.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the commits listed in the advisory (02f8c4fd65f33243ad1f25a98f2af211f9fb7593, 1f8101b6adc87a3ddbd51fcb6609251591758026, 1f9c4b6350ce31e3fccf2a82d47bf35b27167167, 8b21cc8bd182b49415faa24ea9f26b51eea96efb).
  • If a kernel upgrade is not possible, disable the usx2y module or disconnect the affected USB audio device until the patched kernel is available.
  • If the device becomes hung, unload the usx2y module and reload it, or reboot the system to reset the device. Monitor kernel logs for WARN_ON and –ENODEV messages during DSP load attempts and take corrective action if they appear.

Generated by OpenCVE AI on November 18, 2026 at 23:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-594
Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: Refuse a retried DSP load after a failure snd_usx2y_hwdep_dsp_load() sets up the asynchronous sequence URBs and the interrupt URB when the FPGA firmware image with index 1 is loaded, and then creates the ALSA devices. If usx2y_in04_init() or usx2y_create_alsa_devices() fails, the URBs that were already set up are left in place. The core keeps the index unloaded when the callback fails, so user space may issue the same request again. The second attempt then enters usx2y_async_seq04_init() or usx2y_in04_init() with the URBs still allocated and trips WARN_ON(usx2y->as04.buffer) or WARN_ON(usx2y->in04_urb). The URBs cannot be released at this point: the card may already have registered PCM devices that user space can still open, and the disconnect handler accesses the URBs without holding the DSP lock. Mark the chip as hung instead, so that a retried request is refused with -ENODEV and the assertions keep their meaning. The URBs are released by snd_usx2y_card_private_free() when the card is freed. A failing usx2y_async_seq04_init() still releases its own URBs, so that path remains retryable.
Title ALSA: usx2y: Refuse a retried DSP load after a failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-594

    J2EE Framework: Saving Unserializable Objects to Disk

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 18, 2026, 8:42 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Nov 18, 2026, 9:17 AM
Modified
Nov 18, 2026, 9:17 AM