Skip to content
Threat Brief

← All advisories

CVE-2026-99319

High 7.8No known exploitationFix available

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

Record last updated

CVSS score

7.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 8% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 02d382af1c4e321acbea1c25b97ee13f52b9ac7d before 1f9c4b6350ce31e3fccf2a82d47bf35b271671671f9c4b6350ce31e3fccf2a82d47bf35b27167167CVE Program
LinuxLinuxfrom 02d382af1c4e321acbea1c25b97ee13f52b9ac7d before 02f8c4fd65f33243ad1f25a98f2af211f9fb759302f8c4fd65f33243ad1f25a98f2af211f9fb7593CVE Program
LinuxLinuxfrom 02d382af1c4e321acbea1c25b97ee13f52b9ac7d before 8b21cc8bd182b49415faa24ea9f26b51eea96efb8b21cc8bd182b49415faa24ea9f26b51eea96efbCVE Program
LinuxLinuxfrom 02d382af1c4e321acbea1c25b97ee13f52b9ac7d before 1f8101b6adc87a3ddbd51fcb66092515917580261f8101b6adc87a3ddbd51fcb6609251591758026CVE Program
LinuxLinux5.14Not documentedCVE Program
Microsoftazl3 kernel 6.6.161.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.14Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references