Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-50419

8.8 · HIGH

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…

Published Sep 18, 2025CWE-415EPSS 0.24%

Overview

CVE-2022-50419 is a high-severity vulnerability. It was published on September 18, 2025 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

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:

<TASK>

__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_e

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/1b6c89571f453101251201f0fad1c26f7256e937Refgit.kernel.org/stable/c/3423a50fa018e88aed4c900d59c3c8334d8ad583Refgit.kernel.org/stable/c/448a496f760664d3e2e79466aa1787e6abc922b5Refgit.kernel.org/stable/c/4bcefec3636208b4c97536b26014d5935d5c10a0Refgit.kernel.org/stable/c/6144423712d570247b8ca26e50a277c30dd13702Refgit.kernel.org/stable/c/671fee73e08ff415d36a7c16bdf238927df83884Refgit.kernel.org/stable/c/6e85d2ad958c6f034b1b158d904019869dbb3c81Refgit.kernel.org/stable/c/7b674dce4162bb46d396586e30e4653427023875Refgit.kernel.org/stable/c/ef055094df4c10b73cfe67c8d43f9de1fb608a8b

How CyberStrike helps

Frequently asked questions

What is CVE-2022-50419?

CVE-2022-50419 is a high-severity vulnerability. It was published on September 18, 2025 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2022-50419?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2022-50419?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50419?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50419 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999