Adjacent kernel crash via repeated device registration
Published Sep 18, 2025 · Updated Sep 18, 2025
Improper device registration in the Linux kernel Bluetooth subsystem allows adjacent attackers to crash the kernel through LE CIS events. hci_conn_add_sysfs calls device_add again for an HCI connection whose sysfs device was already registered, corrupting the kernel device list. Reachability requires Bluetooth LE Audio or related CIS event handling from a nearby peer or controller; the observed consequence is a kernel BUG and service interruption.
Summary
What happened
Improper device registration in the Linux kernel Bluetooth subsystem allows adjacent attackers to crash the kernel through LE CIS events. hci_conn_add_sysfs calls device_add again for an HCI connection whose sysfs device was already registered, corrupting the kernel device list. Reachability requires Bluetooth LE Audio or related CIS event handling from a nearby peer or controller; the observed consequence is a kernel BUG and service interruption.
The record
- CVE
- CVE-2022-50419
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1b6c89571f453101251201f0fad1c26f7256e937
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3423a50fa018e88aed4c900d59c3c8334d8ad583
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <448a496f760664d3e2e79466aa1787e6abc922b5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4bcefec3636208b4c97536b26014d5935d5c10a0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6144423712d570247b8ca26e50a277c30dd13702
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <671fee73e08ff415d36a7c16bdf238927df83884
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e85d2ad958c6f034b1b158d904019869dbb3c81
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7b674dce4162bb46d396586e30e4653427023875
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ef055094df4c10b73cfe67c8d43f9de1fb608a8b
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