LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50833 is a Linux kernel Bluetooth defect involving internal workqueue handling during device shutdown or cleanup. Public sources do not state a clear security impact, severity score, or active exploitation. Treat it as a kernel stability and availability issue until Linux distribution guidance clarifies risk.

Executive priority

Handle through normal kernel patch governance unless your environment depends heavily on Bluetooth-enabled Linux systems. Escalate priority if your vendor assigns higher severity or identifies availability impact for deployed kernels.

Technical view

The flaw is in Linux Bluetooth HCI workqueue handling. Timer work for command and ncommand timeouts could be queued through the wrong workqueue while the HCI device workqueue was draining. The stable fix queues this work on hdev->workqueue and adds RCU protection around delayed work queuing.

Likely exposure

Exposure is most relevant to Linux systems using affected kernel lines listed in the CVE record, including 5.19.15, 6.0, 6.0.1, and 6.1 entries, especially where Bluetooth HCI support is present. Confirm applicability through your distribution kernel advisory.

Exploitation context

The issue was reported by syzbot. The provided sources do not describe a practical exploit path, attacker requirements, or real-world exploitation. It is not listed as CISA KEV in the provided data.

Researcher notes

Public metadata is incomplete: no CVSS, CWE, or explicit impact is provided. The strongest evidence is the Linux stable commit text describing a workqueue lifecycle bug and its fix. Avoid assuming remote exploitability without vendor confirmation.

Mitigation direction

  • Check your Linux distribution advisory for CVE-2022-50833 applicability and fixed kernel packages.
  • Update affected Linux kernels to a vendor-supported build containing the stable Bluetooth fix.
  • Prioritize systems with Bluetooth enabled or exposed to untrusted Bluetooth interactions.
  • If Bluetooth is unnecessary, consider disabling it according to vendor-approved hardening guidance.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and embedded devices.
  • Identify systems with Bluetooth HCI support enabled or hardware present.
  • Compare installed kernel package changelogs against the referenced stable commits.
  • Confirm patched systems are running the updated kernel after maintenance.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50833 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3b382555706558f5c0587862b6dc03e96a252bba, 877afadad2dce8aae1f2aad8ce47e072d4f6165e, 877afadad2dce8aae1f2aad8ce47e072d4f6165e, 4bf367fa1fefabdf14938d0ac9ed60020389112eunaffected
LinuxLinux6.0, 0, 5.19.15, 6.0.1, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.