Kernel memory corruption via premature USB URB release
Published Jun 18, 2025 · Updated May 11, 2026
Use-after-free in the ALSA bcd2000 USB driver in affected Linux kernel revisions allows local users to corrupt kernel memory during probing. The probe error path frees bcd2k->midi_out_urb before canceling it, so bcd2000_input_complete can access the released allocation. Reachability requires a BCD2000 USB device and an snd_card_register() failure during probing; the published KASAN trace confirms an invalid kernel read.
Summary
What happened
Use-after-free in the ALSA bcd2000 USB driver in affected Linux kernel revisions allows local users to corrupt kernel memory during probing. The probe error path frees bcd2k->midi_out_urb before canceling it, so bcd2000_input_complete can access the released allocation. Reachability requires a BCD2000 USB device and an snd_card_register() failure during probing; the published KASAN trace confirms an invalid kernel read.
The record
- CVE
- CVE-2022-50229
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.16
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <05e0bb8c3c4dde3e21b9c1cf9395afb04e8b24db
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <1d6a246cf97c380f2da76591f03019dd9c9599c3
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <348620464a5c127399ac09b266f494f393661952
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <4fc41f7ebb7efca282f1740ea934d16f33c1d109
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <5e7338f4dd92b2f8915a82abfa1dd3ad3464bea0
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <64ca7f50ad96c2c65ae390b954925a36eabe04aa
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <a718eba7e458e2f40531be3c6b6a0028ca7fcace
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <b0d4af0a4763ddc02344789ef2a281c494bc330d
- Affected versionversion=b47a22290d581277be70e8a597824a4985d39e83 <ffb2759df7efbc00187bfd9d1072434a13a54139
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo