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

> A race condition in the Linux kernel Bluetooth subsystem allows attackers to cause a denial of service via improper workqueue scheduling.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 23 May 2026
- **Also known as:** DEBIAN-CVE-2022-50833, GHSA-rxjc-h4m5-gvq8, UBUNTU-CVE-2022-50833

## What is CVE-2022-50833?

CVE-2022-50833 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2022-50833?


## How do I fix CVE-2022-50833?

Apply the vendor's patch.

## Is CVE-2022-50833 being exploited?

There is no known exploitation of CVE-2022-50833 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50833 and fix it if it is affected.

What it is: CVE-2022-50833 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50833 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50833/ (Markdown: https://insights.sbomify.com/CVE-2022-50833/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50833
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50833
- OSV: https://osv.dev/vulnerability/CVE-2022-50833

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50833/
Summaries are generated and may contain mistakes; the official description above is the record.