CVE-2024-27416: Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST
If we received HCI_EV_IO_CAPA_REQUEST while
HCI_OP_READ_REMOTE_EXT_FEATURES is yet to be responded assume the remote
does support SSP since otherwise this event shouldn't be generated.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Bluetooth pairing-state bug. The kernel mishandled an IO Capability Request if it arrived before the controller answered a remote feature query. Sources confirm kernel stable fixes, but do not provide CVSS, business impact, or exploit evidence. Treat it as Bluetooth-adjacent kernel maintenance unless your fleet exposes Bluetooth on affected kernels.
Executive priority
Prioritize normal kernel patching, with faster handling for laptops, kiosks, embedded systems, or operational devices using Bluetooth. Escalate only if your vendor rates the issue higher or your environment depends on Bluetooth pairing in sensitive workflows.
Technical view
The Bluetooth hci_event path now assumes SSP support when HCI_EV_IO_CAPA_REQUEST arrives while HCI_OP_READ_REMOTE_EXT_FEATURES is still pending, because that event should not occur without SSP. CVE data lists affected Linux versions including 4.19.309, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8, and 6.6.
Likely exposure
Exposure is most relevant to systems running affected Linux kernels with Bluetooth enabled or reachable. Servers with Bluetooth disabled or no Bluetooth hardware are likely lower priority. The source bundle does not define required attacker proximity, privileges, or impact.
Exploitation context
The source bundle shows no CISA KEV listing and provides no public exploitation claim. The available description is a kernel correctness fix around Bluetooth Secure Simple Pairing state handling, not a documented exploit chain.
Researcher notes
Evidence is limited: no CVSS, CWE, exploitability details, or impact class are provided. The description implies a race/order handling issue in Bluetooth event processing around SSP feature assumptions. Analysis should stay anchored to the kernel commits and distribution advisories.
Mitigation direction
Identify Linux systems with Bluetooth enabled and affected kernel versions.
Apply vendor kernel updates that include the referenced stable fixes.
For Debian LTS systems, review the linked Debian security announcements.
Disable Bluetooth where it is not operationally required.
Check your OS vendor guidance for exact fixed package versions.
Validation and detection
Inventory kernel versions across laptops, servers, appliances, and embedded Linux systems.
Confirm whether Bluetooth hardware and services are enabled on each exposed asset.
Map each kernel to vendor advisories or stable commits in the source list.
Verify updated systems boot the corrected vendor kernel.
Document any exceptions where Bluetooth remains enabled on affected kernels.
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-27416 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.