CVE-2022-50419

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-18. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times

device_add shall not be called multiple times as stated in its documentation:

'Do not call this routine or device_register() more than once for any device structure'

Syzkaller reports a bug as follows [1]: ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:33! invalid opcode: 0000 [#1] PREEMPT SMP KASAN [...] Call Trace: __list_add include/linux/list.h:69 [inline] list_add_tail include/linux/list.h:102 [inline] kobj_kset_join lib/kobject.c:164 [inline] kobject_add_internal+0x18f/0x8f0 lib/kobject.c:214 kobject_add_varg lib/kobject.c:358 [inline] kobject_add+0x150/0x1c0 lib/kobject.c:410 device_add+0x368/0x1e90 drivers/base/core.c:3452 hci_conn_add_sysfs+0x9b/0x1b0 net/bluetooth/hci_sysfs.c:53 hci_le_cis_estabilished_evt+0x57c/0xae0 net/bluetooth/hci_event.c:6799 hci_le_meta_evt+0x2b8/0x510 net/bluetooth/hci_event.c:7110 hci_event_func net/bluetooth/hci_event.c:7440 [inline] hci_event_packet+0x63d/0xfd0 net/bluetooth/hci_event.c:7495 hci_rx_work+0xae7/0x1230 net/bluetooth/hci_core.c:4007 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

September 18, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef055094df4c10b73cfe67c8d43f9de1fb608a8b
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b674dce4162bb46d396586e30e4653427023875
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e85d2ad958c6f034b1b158d904019869dbb3c81
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/671fee73e08ff415d36a7c16bdf238927df83884
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6144423712d570247b8ca26e50a277c30dd13702
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4bcefec3636208b4c97536b26014d5935d5c10a0
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/448a496f760664d3e2e79466aa1787e6abc922b5
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3423a50fa018e88aed4c900d59c3c8334d8ad583
generic

Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b6c89571f453101251201f0fad1c26f7256e937

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.331—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)5.10.158-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-09-16 14:05 UTCEPSS rescore
  2. 2026-09-16 05:11 UTCEPSS rescore
  3. 2026-09-15 03:07 UTCEPSS rescore
  4. 2026-09-13 16:44 UTCEPSS rescore
  5. 2026-09-11 14:50 UTCEPSS rescore
  6. 2026-09-11 09:34 UTCEPSS rescore
  7. 2026-09-08 21:57 UTCEPSS rescore
  8. 2026-09-07 15:59 UTCEPSS rescore
  9. 2026-09-07 04:18 UTCOSV refresh
  10. 2026-09-06 13:45 UTCEPSS rescore
  11. 2026-09-05 15:25 UTCEPSS rescore
  12. 2026-09-04 13:57 UTCEPSS rescore
  13. 2026-09-04 05:04 UTCEPSS rescore
  14. 2026-09-02 14:09 UTCEPSS rescore
  15. 2026-09-01 13:51 UTCEPSS rescore
  16. 2026-08-30 19:15 UTCEPSS rescore
  17. 2026-08-30 01:19 UTCEPSS rescore
  18. 2026-08-28 21:38 UTCEPSS rescore
  19. 2026-08-27 14:22 UTCEPSS rescore
  20. 2026-08-26 14:43 UTCEPSS rescore
  21. 2026-08-25 13:46 UTCEPSS rescore
  22. 2026-08-21 23:46 UTCEPSS rescore
  23. 2026-08-20 22:53 UTCEPSS rescore
  24. 2026-08-20 14:01 UTCOSV refresh
  25. 2026-08-19 17:01 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:45 UTCEPSS rescore
  2. 2026-08-17 13:44 UTCEPSS rescore
  3. 2026-08-16 14:53 UTCEPSS rescore
  4. 2026-08-16 02:12 UTCEPSS rescore
  5. 2026-08-15 01:27 UTCEPSS rescore
  6. 2026-08-13 21:58 UTCEPSS rescore
  7. 2026-08-12 13:48 UTCEPSS rescore
  8. 2026-08-09 13:44 UTCEPSS rescore
  9. 2026-08-09 13:44 UTCEPSS rescore
  10. 2026-08-08 16:34 UTCEPSS rescore
  11. 2026-08-07 16:24 UTCEPSS rescore
  12. 2026-08-06 13:44 UTCEPSS rescore
  13. 2026-08-05 19:15 UTCEPSS rescore
  14. 2026-08-05 09:19 UTCEG score recompute
  15. 2026-08-05 09:19 UTCGHSA enrichment
  16. 2026-08-04 15:07 UTCEPSS rescore
  17. 2026-08-04 10:58 UTCEG score recompute
  18. 2026-08-04 10:58 UTCGHSA enrichment
  19. 2026-08-04 10:35 UTCEPSS rescore
  20. 2026-08-04 09:30 UTCEG score recompute
  21. 2026-08-04 09:30 UTCGHSA enrichment
  22. 2026-08-03 10:33 UTCEPSS rescore
  23. 2026-08-02 02:24 UTCEPSS rescore
  24. 2026-08-01 04:13 UTCEPSS rescore
  25. 2026-08-01 04:13 UTCEPSS rescore
  26. 2026-07-30 16:25 UTCEPSS rescore
  27. 2026-07-30 01:28 UTCEPSS rescore
  28. 2026-07-28 15:34 UTCEPSS rescore
  29. 2026-07-26 14:52 UTCEPSS rescore
  30. 2026-07-26 14:52 UTCEPSS rescore
  31. 2026-07-25 14:16 UTCEPSS rescore
  32. 2026-07-24 14:15 UTCEPSS rescore
  33. 2026-07-23 20:11 UTCOSV refresh
  34. 2026-07-23 14:16 UTCEPSS rescore
  35. 2026-07-23 14:16 UTCEPSS rescore
  36. 2026-07-23 02:17 UTCEG score recompute
  37. 2026-07-22 23:04 UTCEG score recompute
  38. 2026-07-22 14:06 UTCEPSS rescore
  39. 2026-07-22 14:06 UTCEPSS rescore
  40. 2026-07-21 15:23 UTCEPSS rescore
  41. 2026-07-21 15:23 UTCEPSS rescore
  42. 2026-07-20 17:05 UTCEPSS rescore
  43. 2026-07-19 14:29 UTCEPSS rescore
  44. 2026-07-19 14:29 UTCEPSS rescore
  45. 2026-07-18 10:03 UTCEPSS rescore
  46. 2026-07-18 10:03 UTCEPSS rescore
  47. 2026-07-16 17:00 UTCEPSS rescore
  48. 2026-07-15 16:56 UTCEPSS rescore
  49. 2026-07-15 16:56 UTCEPSS rescore
  50. 2026-07-15 01:58 UTCEPSS rescore
  51. 2026-07-15 01:58 UTCEPSS rescore
  52. 2026-07-13 22:28 UTCEPSS rescore
  53. 2026-07-13 22:28 UTCEPSS rescore
  54. 2026-07-13 06:11 UTCEPSS rescore
  55. 2026-07-13 06:11 UTCEPSS rescore
  56. 2026-07-12 05:44 UTCEPSS rescore
  57. 2026-07-11 08:25 UTCEPSS rescore
  58. 2026-07-11 08:25 UTCEPSS rescore
  59. 2026-07-09 19:08 UTCEPSS rescore
  60. 2026-07-08 15:13 UTCEPSS rescore
  61. 2026-07-07 13:44 UTCEPSS rescore
  62. 2026-07-06 16:25 UTCEPSS rescore
  63. 2026-07-06 14:11 UTCOSV refresh
  64. 2026-07-06 02:21 UTCEPSS rescore
  65. 2026-07-05 02:28 UTCEPSS rescore
  66. 2026-07-04 06:29 UTCEPSS rescore
  67. 2026-07-01 15:04 UTCEPSS rescore
  68. 2026-06-30 23:21 UTCEPSS rescore
  69. 2026-06-30 23:20 UTCEPSS rescore
  70. 2026-06-29 14:04 UTCEPSS rescore
  71. 2026-06-28 14:06 UTCEPSS rescore
  72. 2026-06-28 04:54 UTCEPSS rescore
  73. 2026-06-28 04:54 UTCEPSS rescore
  74. 2026-06-27 03:07 UTCEPSS rescore
  75. 2026-06-27 03:07 UTCEPSS rescore

Frequently asked(5)

What is CVE-2022-50419?
CVE-2022-50419 is a high vulnerability published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisysfs: Fix attempting to call deviceadd multiple times device_add shall not be called multiple times as stated in its documentation: 'Do not call this routine or device_register() more than once for any device…
When was CVE-2022-50419 disclosed?
CVE-2022-50419 was first published in the National Vulnerability Database on September 18, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50419 actively exploited?
CVE-2022-50419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.2% of all scored CVEs.
What is the CVSS score of CVE-2022-50419?
CVE-2022-50419 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50419, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50419

Explore →

Is Your Infrastructure Affected by CVE-2022-50419?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs