CVE-2022-50833

Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works

N/A
Published: December 30, 2025 at 12:10 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works syzbot is reporting attempt to schedule hdev->cmd_work work from system_wq WQ into hdev->workqueue WQ which is under draining operation [1], for commit c8efcc2589464ac7 ("workqueue: allow chained queueing during destruction") does not allow such operation. The check introduced by commit 877afadad2dce8aa ("Bluetooth: When HCI work queue is drained, only queue chained work") was incomplete. Use hdev->workqueue WQ when queuing hdev->{cmd,ncmd}_timer works because hci_{cmd,ncmd}_timeout() calls queue_work(hdev->workqueue). Also, protect the queuing operation with RCU read lock in order to avoid calling queue_delayed_work() after cancel_delayed_work() completed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.18.185.18.18 ≤ v < 5.195.19.2 ≤ v < 5.19.156.0 ≤ v < 6.0.16.0 ≤ v < 6.13b382555706558f5c0587862b6dc03e96a252bba4bf367fa1fefabdf14938d0ac9ed60020389112e5.18.185.19.26.0877afadad2dce8aae1f2aad8ce47e072d4f6165e
Vendor states this is fixed in 3c6b036fe5c8ed8b6c4cbdc03605929882907ef0 (fixed)
Vendor states this is fixed in c4635cf3d845a7324c25c52d549b70c8bd7ad4c7 (fixed)
Vendor states this is fixed in deee93d13d385103205879a8a0915036ecd83261 (fixed)
Affected range stops below 5.19, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.19.15 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.0.1 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card