Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 54 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1f9c4b6350ce31e3fccf2a82d47bf35b27167167
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 02f8c4fd65f33243ad1f25a98f2af211f9fb7593
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8b21cc8bd182b49415faa24ea9f26b51eea96efb
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1f8101b6adc87a3ddbd51fcb6609251591758026
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.12.118 – ≤ 6.12.*
    • unaffected 6.18.64 – ≤ 6.18.*
    • unaffected 7.3.5 – ≤ 7.3.*
    • unaffected 7.4-rc2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99319 badge
[![CVE-2026-99319](https://cveledger.app/badge/CVE-2026-99319.svg)](https://cveledger.app/cve/CVE-2026-99319)

Record last updated .