LiveActive security incident?Get immediate response
CVE Record

CVE-2024-41063: Bluetooth: hci_core: cancel all works upon hci_unregister_dev()

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: cancel all works upon hci_unregister_dev() syzbot is reporting that calling hci_release_dev() from hci_error_reset() due to hci_dev_put() from hci_error_reset() can cause deadlock at destroy_workqueue(), for hci_error_reset() is called from hdev->req_workqueue which destroy_workqueue() needs to flush. We need to make sure that hdev->{rx_work,cmd_work,tx_work} which are queued into hdev->workqueue and hdev->{power_on,error_reset} which are queued into hdev->req_workqueue are no longer running by the moment destroy_workqueue(hdev->workqueue); destroy_workqueue(hdev->req_workqueue); are called from hci_release_dev(). Call cancel_work_sync() on these work items from hci_unregister_dev() as soon as hdev->list is removed from hci_dev_list.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-41063 is a Linux kernel Bluetooth bug where cleanup of a Bluetooth device can deadlock if queued work is still running. The visible business risk is system availability or reliability on Linux hosts using Bluetooth/HCI functionality, not confirmed data theft or remote compromise.

Executive priority

Track this as an availability reliability issue unless local exposure shows Bluetooth is widely enabled on critical systems. Patch through normal kernel maintenance, escalating for endpoints, kiosks, labs, or embedded Linux systems using Bluetooth.

Technical view

The issue is in Linux Bluetooth hci_core. During hci_unregister_dev()/hci_release_dev(), workqueues can be destroyed while hci_error_reset() or related work items are still active. The fix cancels rx_work, cmd_work, tx_work, power_on, and error_reset before workqueue destruction.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with Bluetooth/HCI device support active. Systems without Bluetooth hardware, disabled Bluetooth, or fixed vendor kernels are less likely to be exposed. The bundle does not provide distribution-wide applicability beyond the Debian LTS notice.

Exploitation context

The source bundle cites syzbot discovery and kernel deadlock behavior. It does not cite public exploitation, weaponized proof of concept, KEV listing, or remote attack confirmation. KEV is false, so active exploitation should not be assumed.

Researcher notes

Evidence supports a workqueue lifecycle deadlock in the Bluetooth HCI core, fixed by synchronously canceling relevant work items during unregister. Severity, CVSS, CWE, exploitability, and attacker prerequisites are not supplied, limiting confidence in operational risk ranking.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable Bluetooth hci_core fixes.
  • Check Debian LTS guidance if running affected Debian LTS kernel packages.
  • Prioritize systems where Bluetooth/HCI is enabled or exposed to untrusted devices.
  • If no vendor fix is available, monitor vendor advisories for backports.

Validation and detection

  • Inventory Linux kernel versions across systems with Bluetooth enabled.
  • Confirm whether the deployed kernel includes one of the referenced stable commits.
  • Check vendor advisory status for each distribution and kernel package.
  • Review crash or hang telemetry for Bluetooth-related kernel deadlocks.
Prepared
Confidence
medium
Sources
11

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-2024-41063 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
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe0b278650f07acf2e0932149183458468a731c03, 98fb98fd37e42fd4ce13ff657ea64503e24b6090, 6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2, da4569d450b193e39e87119fd316c0291b585d14, 45085686b9559bfbe3a4f41d3d695a520668f5e1, 2ab9a19d896f5a0dd386e1f001c5309bc35f433b, 2449007d3f73b2842c9734f45f0aadb522daf592, 2449007d3f73b2842c9734f45f0aadb522daf592, dd594cdc24f2e48dab441732e6dfcafd6b0711d1, 4.19.309, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9unaffected
LinuxLinux6.8, 0, 4.19.319, 5.4.281, 5.10.223, 5.15.164, 6.1.101, 6.6.42, 6.9.11, 6.10affected
Weakness

CWE details

No CWE listed

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