CVE-2024-58241: Bluetooth: hci_core: Disable works on hci_unregister_dev
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: Disable works on hci_unregister_dev
This make use of disable_work_* on hci_unregister_dev since the hci_dev is
about to be freed new submissions are not disarable.
Security readout for executives and security teams
Plain-English summary
CVE-2024-58241 is a Linux kernel Bluetooth flaw that can crash or disrupt a system locally. It affects availability, not data theft or tampering, based on the provided CVSS vector. Business urgency is moderate: patch kernels in normal maintenance cycles, faster on shared systems where local users can run code.
Executive priority
Treat this as a moderate availability risk. It does not indicate remote compromise or data exposure, but local users may be able to disrupt affected Linux systems. Patch through standard kernel update processes, with higher urgency for multi-user or operationally critical hosts.
Technical view
The issue is in Linux Bluetooth hci_core during hci_unregister_dev. Work items were not disabled while the hci_dev object was being freed, creating an availability-impacting race or lifetime problem. CVSS is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is limited to Linux systems with affected kernel versions and relevant Bluetooth HCI code present. The bundle marks Linux 6.10, 6.11.6, and 6.12 as affected, while listing several stable releases and commits as unaffected or fixed. Distribution backports may change practical exposure.
Exploitation context
The provided sources do not report active exploitation, and KEV is false. The CVSS vector requires local access with low privileges. No exploit details are provided in the source bundle, so exploitation feasibility beyond the CVSS attributes is not evidenced here.
Researcher notes
Evidence is limited to the CVE record, CVE List data, and two kernel stable references. The affected-version data appears sparse and includes commit identifiers plus selected kernel releases, so validate against vendor backports before declaring systems vulnerable or fixed.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
For custom kernels, review and integrate the linked upstream stable commits.
Prioritize shared Linux hosts where untrusted local users can execute code.
Track distribution advisories for backported fixes and corrected version ranges.
If patch timing is uncertain, follow vendor guidance for interim risk reduction.
Validation and detection
Inventory Linux kernel versions across systems using approved asset data.
Confirm whether installed kernels include the referenced stable fix commits.
Check vendor advisories for backport status, not only upstream version numbers.
Verify Bluetooth-related kernel components are present where exposure is suspected.
Retest after kernel update and confirm the fixed package is running.
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-58241 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.