CVE-2026-99319

Not scored yetLast modified Nov 18, 2026

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.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1f9c4b6350ce31e3fccf2a82d47bf35b27167167; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 02f8c4fd65f33243ad1f25a98f2af211f9fb7593; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 8b21cc8bd182b49415faa24ea9f26b51eea96efb; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1f8101b6adc87a3ddbd51fcb6609251591758026
LinuxLinux2.6.12

References

Timeline

Published
Nov 18, 2026
Last modified
Nov 18, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-99328.3Use after free in ANGLE in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer proceCVE-2026-99337.5Use after free in Input in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who convinced a user to engage in specific UI gesCVE-2026-99347.5Use after free in Aura in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who convinced a user to engage in specific UI gestCVE-2026-99354.3Uninitialized Use in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a crafted HTML pCVE-2026-99368.3Use after free in GFX in Google Chrome on Mac prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to CVE-2026-99378.3Use after free in UI in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process CVE-2026-99388.8Inappropriate implementation in V8 in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sanCVE-2026-99398.8Heap buffer overflow in WebCodecs in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sandCVE-2026-99408.8Heap buffer overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially exploit heap corruption via CVE-2026-99418.8Use after free in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sandbox via a CVE-2026-99425.0Uninitialized Use in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to byCVE-2026-99434.3Out of bounds read in WebGL in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a cr
CVE-2026-99319: Unscored | Vulnix