- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The ALSA usx2y driver in the Linux kernel keeps its asynchronous request buffers allocated when a DSP firmware load fails, so a retried load request from user space can trigger kernel warnings. The fix refuses such retries with -ENODEV instead.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99319 (ALSA: usx2y: Refuse a retried DSP load after a failure), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99319 (entry last updated 2026-11-18):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 2.6.12
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99319 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99319 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/1f9c4b6350ce31e3fccf2a82d47bf35b27167167
- https://git.kernel.org/stable/c/02f8c4fd65f33243ad1f25a98f2af211f9fb7593
- https://git.kernel.org/stable/c/8b21cc8bd182b49415faa24ea9f26b51eea96efb
- https://git.kernel.org/stable/c/1f8101b6adc87a3ddbd51fcb6609251591758026
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99319
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99319"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.12
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99319 |
| Record | NVD · CVE-2026-99319 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/1f9c4b6350ce31e3fccf2a82d47bf35b27167167 |
| Link | git.kernel.org · stable/c/02f8c4fd65f33243ad1f25a98f2af211f9fb7593 |
| Link | git.kernel.org · stable/c/8b21cc8bd182b49415faa24ea9f26b51eea96efb |
| Link | git.kernel.org · stable/c/1f8101b6adc87a3ddbd51fcb6609251591758026 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-99319
Is CVE-2026-99319 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-99319?
Linux: version 2.6.12.Source: cve.now feed data