Security readout for executives and security teams
Plain-English summary
This Linux kernel Bluetooth flaw can crash or corrupt kernel object handling when the same Bluetooth device structure is added more than once. The reported impact is high, but the source bundle indicates local access is required and does not show active exploitation.
Executive priority
Treat as high-priority kernel maintenance, not an emergency exploitation event. Patch quickly on endpoints and shared Linux systems where local users or Bluetooth are present.
Technical view
The bug is in Linux Bluetooth hci_sysfs. Calling device_add more than once for the same device can trigger kobject/list corruption and a kernel BUG. The trace comes from Syzkaller during Bluetooth LE CIS event handling. CVSS is 7.8, local, low complexity, low privileges, no user interaction.
Likely exposure
Linux systems running affected kernel versions are relevant, especially where Bluetooth functionality is enabled. Exposure should be confirmed through kernel version, distro backport status, and whether the referenced stable fixes are present.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. Evidence is a Syzkaller-triggered kernel bug report and Linux stable fixes, not a confirmed in-the-wild attack.
Researcher notes
The affected data in the bundle is version-oriented and incomplete for distro backports. Validate against vendor kernel changelogs and the listed git.kernel.org commits rather than upstream version strings alone.
Mitigation direction
- Apply vendor or distro kernel updates that include the referenced Linux stable fixes.
- If Bluetooth is unnecessary, disable or restrict Bluetooth until patched.
- Check vendor advisories for backported fixes before assuming version numbers are vulnerable.
- Prioritize shared workstations, laptops, and systems with local user access.
Validation and detection
- Inventory Linux kernel versions across affected assets.
- Confirm whether distro kernels include the referenced stable commits or equivalent backports.
- Identify systems with Bluetooth enabled or Bluetooth hardware exposed.
- Review kernel crash logs for related Bluetooth hci_sysfs or kobject BUG traces.
Public sources used
- CVE Program
- CVE List V5
- Linux stable fix 4bcefec3636208b4c97536b26014d5935d5c10a0
- Linux stable fix 6144423712d570247b8ca26e50a277c30dd13702
- Linux stable fix 671fee73e08ff415d36a7c16bdf238927df83884
- Linux stable fix 6e85d2ad958c6f034b1b158d904019869dbb3c81
- Linux stable fix 7b674dce4162bb46d396586e30e4653427023875
- Linux stable fix 3423a50fa018e88aed4c900d59c3c8334d8ad583
- Linux stable fix ef055094df4c10b73cfe67c8d43f9de1fb608a8b
- Linux stable fix 1b6c89571f453101251201f0fad1c26f7256e937
- Linux stable fix 448a496f760664d3e2e79466aa1787e6abc922b5
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-50419 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/4bcefec3636208b4c97536b26014d5935d5c10a0CVE reference
- https://git.kernel.org/stable/c/6144423712d570247b8ca26e50a277c30dd13702CVE reference
- https://git.kernel.org/stable/c/671fee73e08ff415d36a7c16bdf238927df83884CVE reference
- https://git.kernel.org/stable/c/6e85d2ad958c6f034b1b158d904019869dbb3c81CVE reference
- https://git.kernel.org/stable/c/7b674dce4162bb46d396586e30e4653427023875CVE reference
- https://git.kernel.org/stable/c/3423a50fa018e88aed4c900d59c3c8334d8ad583CVE reference
- https://git.kernel.org/stable/c/ef055094df4c10b73cfe67c8d43f9de1fb608a8bCVE reference
- https://git.kernel.org/stable/c/1b6c89571f453101251201f0fad1c26f7256e937CVE reference
- https://git.kernel.org/stable/c/448a496f760664d3e2e79466aa1787e6abc922b5CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Double Free
Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.