CVE-2026-99319: ALSA: usx2y: Refuse a retried DSP load after a failure

Published Nov 18, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

sndusx2yhwdepdspload() 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 usx2yin04init() or usx2ycreatealsadevices() 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 usx2yasyncseq04init() or usx2yin04init() with the URBs still allocated and trips WARNON(usx2y->as04.buffer) or WARNON(usx2y->in04urb).

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 sndusx2ycardprivatefree() when the card is freed.

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

Affected Software

1 affected component
Linux Linux kernel ALSA usx2y driver

Event History

Nov 18, 2026
CVE Published
via MITRE·08:42 AM
Data Sourced
via MITRE·08:42 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this condition?

Systems using the Linux kernel ALSA usx2y driver are affected when loading the FPGA firmware image with index 1. The problematic state occurs only if usx2y_in04_init() or usx2y_create_alsa_devices() fails after asynchronous sequence and interrupt URBs have already been set up.

2

What is required to trigger the warning condition?

A DSP load must fail in one of the affected initialization or ALSA-device creation paths, and user space must then retry the same DSP load request. The retained URBs cause the retry to reach assertions for an already allocated asynchronous-sequence buffer or interrupt URB.

3

How does the fix change retry behavior?

After the relevant failed load, the driver marks the chip as hung and rejects a repeated request with -ENODEV. The URBs remain allocated until the card is freed, while failures in usx2y_async_seq04_init() remain retryable because that path releases its own URBs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203