CVE-2024-35933: Bluetooth: btintel: Fix null ptr deref in btintel_read_version
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btintel: Fix null ptr deref in btintel_read_version
If hci_cmd_sync_complete() is triggered and skb is NULL, then
hdev->req_skb is NULL, which will cause this issue.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Bluetooth bug in Intel Bluetooth handling that can dereference a null pointer. In business terms, the main concern is availability on systems using affected kernels and Bluetooth support. The source bundle does not provide CVSS, confirmed exploitation, or detailed attacker requirements.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize laptops, workstations, embedded devices, and appliances using Linux Bluetooth support, especially where downtime would affect operations.
Technical view
CVE-2024-35933 affects the Linux kernel btintel Bluetooth path. The fix addresses a null pointer dereference in btintel_read_version when hci_cmd_sync_complete() is triggered with skb as NULL, leaving hdev->req_skb NULL. Stable kernel commits and Debian LTS advisories are cited as remediation sources.
Likely exposure
Likely exposure is Linux systems running affected kernel versions with Intel Bluetooth support enabled or present. Systems without Bluetooth hardware/modules, or kernels containing the referenced stable fixes, are less likely exposed. The bundle does not provide a complete distribution package matrix.
Exploitation context
No provided source states active exploitation, and KEV is false. The available evidence describes a kernel null pointer dereference, suggesting possible denial-of-service impact, but attacker position, trigger reliability, and real-world exploitation are not established in the bundle.
Researcher notes
The record lacks CVSS, CWE, and detailed exploitability data. Analysis should focus on affected kernel lineage, btintel exposure, distribution backports, and whether the vulnerable path is reachable in local hardware configurations.
Mitigation direction
Apply vendor kernel updates that include the referenced stable commits.
Review Debian LTS advisories if running affected Debian releases.
Check Linux distribution security guidance for exact fixed package versions.
Disable or remove unnecessary Bluetooth support where operationally feasible.
Validation and detection
Inventory Linux hosts with Bluetooth hardware or btintel module usage.
Compare running kernel versions against vendor fixed releases.
Confirm patched kernels include the referenced upstream stable commits.
Monitor vendor advisories for updated severity or exploit information.
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-35933 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.