Linux Kernel up to 6.12.117/6.18.63/7.3.4/7.4-rc1 ALSA usx2y Driver snd_usx2y_hwdep_dsp_load as04/in04_urb allocation of resources

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Linux Kernel up to 6.12.117/6.18.63/7.3.4/7.4-rc1 and classified as problematic. Affected is the function snd_usx2y_hwdep_dsp_load of the component ALSA usx2y Driver. Executing a manipulation of the argument as04/in04_urb can lead to allocation of resources.
This vulnerability is registered as CVE-2026-99319. The attack needs to be launched locally. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Linux Kernel up to 6.12.117/6.18.63/7.3.4/7.4-rc1 and classified as problematic. This vulnerability affects the function snd_usx2y_hwdep_dsp_load of the component ALSA usx2y Driver. The manipulation of the argument as04/in04_urb with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. As an impact it is known to affect availability. CVE summarizes:
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.
The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-99319 since 09/25/2026. The exploitation appears to be easy. The attack needs to be approached locally. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
Upgrading to version 6.12.118, 6.18.64, 7.3.5 or 7.4-rc2 eliminates this vulnerability. Applying the patch 1f9c4b6350ce31e3fccf2a82d47bf35b27167167/8b21cc8bd182b49415faa24ea9f26b51eea96efb/1f8101b6adc87a3ddbd51fcb6609251591758026 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-128490). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 6.12.117
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
- 6.18.53
- 6.18.54
- 6.18.55
- 6.18.56
- 6.18.57
- 6.18.58
- 6.18.59
- 6.18.60
- 6.18.61
- 6.18.62
- 6.18.63
- 7.3.0
- 7.3.1
- 7.3.2
- 7.3.3
- 7.3.4
- 7.4-rc1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.12.118/6.18.64/7.3.5/7.4-rc2
Patch: 1f9c4b6350ce31e3fccf2a82d47bf35b27167167/8b21cc8bd182b49415faa24ea9f26b51eea96efb/1f8101b6adc87a3ddbd51fcb6609251591758026
Timeline
09/25/2026 CVE reserved11/18/2026 Advisory disclosed
11/18/2026 VulDB entry created
11/18/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CNA: Linux
CVE: CVE-2026-99319 (🔒)
GCVE (CVE): GCVE-0-2026-99319
GCVE (VulDB): GCVE-100-439240
EUVD: 🔒
Entry
Created: 11/18/2026 10:09Updated: 11/18/2026 10:36
Changes: 11/18/2026 10:09 (60), 11/18/2026 10:36 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.