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-98316ALSA: bcd2000: Fix race between rawmidi and disconnect

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: Fix race between rawmidi and disconnect Although we tried to fix the potential UAF issues at USB disconnect on bcd2000 driver, there is still an overlooked case -- namely, when a rawmidi trigger callback has been already running at USB disconnect handling, the in-flight function (e.g. bcd2000_midi_send()) could still access the URB, because the previous URB NULL-check & clearance was considered only for the URB complete callbacks, but not about the parallel rawmidi operations. For addressing the race, this patch introduced a new spinlock that covers each rawmidi operation as well as the rawmidi handling in the complete callback. The URB is cleared with the lock, so it guarantees that the pending rawmidi task already finished or a NULL check is effective.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

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)
0.17% · top 93% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3c00004f134fc819f9d9e202c6a64acde0a1f8d0 – < 3b824930259d54f5047ce6b5c97bd20db2fc2b98
    • affected 6c07aad8a7c9ef8ebc4d03a964b882123a349a2e – < c83d6b0a65f7b71bbabcc91c045dfbffdff6ae76
    • affected eb482a06791d6168beb8c78cc904ac5a5ed96a55 – < 0a7ecf52cb59ed77ec525deb52c496ea8fba10b1
    • affected 7df3194bdb7479cad9199889655a566a2c0c1d1b – < 812ca56867bec3065c2a27f1ff5ce04e2a8bf4f0
    • affected b06ebc7fe25a6af4a9f6e4a3d4236a4178ad4b01 – < 9c8b6eff6e7505c128b615d9a1364ef66fa5c18e
    • affected 459d3a64766f5ca2f1886daeaf24582831a5f5ab – < 221253723dc58bb901c3f27a7659823e63fc598c
    • affected 9af08677aa57debaca5b57c8045c52a83d3dd376
    • affected 5a77febac6faf6da40fbb4555f703eeb91b58130
    • affected 5.10.270 – < 5.11
    • affected 5.15.221 – < 5.16
  • Linux · Linux

    • affected 6.1.188 – < 6.1.189
    • affected 6.6.157 – < 6.6.158
    • affected 6.12.109 – < 6.12.112
    • affected 6.18.50 – < 6.18.54
    • affected 7.2.4 – < 7.2.8

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .