CVE-2022-50166

published 18 Jun 2025 · updated 7 Nov 2026

Bluetooth: When HCI work queue is drained, only queue chained work

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 877afadad2dce8aae1f2aad8ce47e072d4f6165e, Kernel 5.19.2, Kernel 4bf367fa1fefabdf14938d0ac9ed60020389112e and 2 more.

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: When HCI work queue is drained, only queue chained work The HCI command, event, and data packet processing workqueue is drained to avoid deadlock in commit 76727c02c1e1 ("Bluetooth: Call drain_workqueue() before resetting state"). There is another delayed work, which will queue command to this drained workqueue. Which results in the following error report: Bluetooth: hci2: command 0x040f tx timeout WARNING: CPU: 1 PID: 18374 at kernel/workqueue.c:1438 __queue_work+0xdad/0x1140 Workqueue: events hci_cmd_timeout RIP: 0010:__queue_work+0xdad/0x1140 RSP: 0000:ffffc90002cffc60 EFLAGS: 00010093 RAX: 0000000000000000 RBX: ffff8880b9d3ec00 RCX: 0000000000000000 RDX: ffff888024ba0000 RSI: ffffffff814e048d RDI: ffff8880b9d3ec08 RBP: 0000000000000008 R08: 0000000000000000 R09: 00000000b9d39700 R10: ffffffff814f73c6 R11: 0000000000000000 R12: ffff88807cce4c60 R13: 0000000000000000 R14: ffff8880796d8800 R15: ffff8880796d8800 FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000c0174b4000 CR3: 000000007cae9000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? queue_work_on+0xcb/0x110 ? lockdep_hardirqs_off+0x90/0xd0 queue_work_on+0xee/0x110 process_one_work+0x996/0x1610 ? pwq_dec_nr_in_flight+0x2a0/0x2a0 ? rwlock_bug.part.0+0x90/0x90 ? _raw_spin_lock_irq+0x41/0x50 worker_thread+0x665/0x1080 ? process_one_work+0x1610/0x1610 kthread+0x2e9/0x3a0 ? kthread_complete_and_exit+0x40/0x40 ret_from_fork+0x1f/0x30 </TASK> To fix this, we can add a new HCI_DRAIN_WQ flag, and don't queue the timeout workqueue while command workqueue is draining.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=76727c02c1e14a2b561b806fa1d08acc1619ad27 <877afadad2dce8aae1f2aad8ce47e072d4f6165e, >=5.19 <5.19.2, >=76727c02c1e14a2b561b806fa1d08acc1619ad27 <4bf367fa1fefabdf14938d0ac9ed60020389112e, >=3.19 <5.18.18, =3.19, >=76727c02c1e14a2b561b806fa1d08acc1619ad27 <3b382555706558f5c0587862b6dc03e96a252bba877afadad2dce8aae1f2aad8ce47e072d4f6165e, 5.19.2, 4bf367fa1fefabdf14938d0ac9ed60020389112e, 5.18.18, 3b382555706558f5c0587862b6dc03e96a252bba
linux-kernel: Kernel>=3.19.0 <5.18.18, >=5.19.0 <5.19.25.18.18, 5.19.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50166 severity on Zeptric[![CVE-2022-50166](https://zeptric.io/badge/cve/CVE-2022-50166.svg)](https://zeptric.io/cve/CVE-2022-50166)