CVE-2026-98316: ALSA: bcd2000: Fix race between rawmidi and disconnect
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 0a7ecf52cb59ed77ec525deb52c496ea8fba10b1, 221253723dc58bb901c3f27a7659823e63fc598c, 3b824930259d54f5047ce6b5c97bd20db2fc2b98; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 0a7ecf52cb59ed77ec525deb52c496ea8fba10b1, 221253723dc58bb901c3f27a7659823e63fc598c, 3b824930259d54f5047ce6b5c97bd20db2fc2b98; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 9af08677aa57debaca5b57c8045c52a83d3dd376, 5a77febac6faf6da40fbb4555f703eeb91b58130affected
- 3c00004f134fc819f9d9e202c6a64acde0a1f8d0 and later · before 3b824930259d54f5047ce6b5c97bd20db2fc2b98affected · git
- 6c07aad8a7c9ef8ebc4d03a964b882123a349a2e and later · before c83d6b0a65f7b71bbabcc91c045dfbffdff6ae76affected · git
- eb482a06791d6168beb8c78cc904ac5a5ed96a55 and later · before 0a7ecf52cb59ed77ec525deb52c496ea8fba10b1affected · git
- 7df3194bdb7479cad9199889655a566a2c0c1d1b and later · before 812ca56867bec3065c2a27f1ff5ce04e2a8bf4f0affected · git
- b06ebc7fe25a6af4a9f6e4a3d4236a4178ad4b01 and later · before 9c8b6eff6e7505c128b615d9a1364ef66fa5c18eaffected · git
- 459d3a64766f5ca2f1886daeaf24582831a5f5ab and later · before 221253723dc58bb901c3f27a7659823e63fc598caffected · git
- 5.10.270 and later · before 5.11affected · semver
- 5.15.221 and later · before 5.16affected · semver
- 6.1.188 and later · before 6.1.189affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98314Oct 6, 2026 · ALSA: pcm: set timer->private_data before registering the PCM timer0Monitor
- ← EarlierCVE-2026-98315Oct 6, 2026 · ntfs: protect runlist updates with the runlist lock31Monitor
- Later →CVE-2026-98317Oct 6, 2026 · neighbour: Enforce min/max to NDTPA_INTERVAL_PROBE_TIME_MS.0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a7ecf52cb59ed77ec525deb52c496ea8fba10b1 | Vendor (CNA) |
| Linux Linux | 221253723dc58bb901c3f27a7659823e63fc598c | Vendor (CNA) |
| Linux Linux | 3b824930259d54f5047ce6b5c97bd20db2fc2b98 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.12.112 | Vendor (CNA) |
| Linux Linux | 6.18.54 | Vendor (CNA) |
| Linux Linux | 6.6.158 | Vendor (CNA) |
| Linux Linux | 7.2.8 | Vendor (CNA) |
| Linux Linux | 812ca56867bec3065c2a27f1ff5ce04e2a8bf4f0 | Vendor (CNA) |
| Linux Linux | 9c8b6eff6e7505c128b615d9a1364ef66fa5c18e | Vendor (CNA) |
| Linux Linux | c83d6b0a65f7b71bbabcc91c045dfbffdff6ae76 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+38 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/221253723dc58bb901c3f27a7659823e63fc598c
- git.kernel.org/stable/c/3b824930259d54f5047ce6b5c97bd20db2fc2b98
- git.kernel.org/stable/c/812ca56867bec3065c2a27f1ff5ce04e2a8bf4f0
- git.kernel.org/stable/c/9c8b6eff6e7505c128b615d9a1364ef66fa5c18e
- git.kernel.org/stable/c/c83d6b0a65f7b71bbabcc91c045dfbffdff6ae76
Vendor advisories and official records. Exploit/PoC links are deliberately left out.