CVE-2024-36033: Bluetooth: qca: fix info leak when fetching board id
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: qca: fix info leak when fetching board id
Add the missing sanity check when fetching the board id to avoid leaking
slab data when later requesting the firmware.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel information leak in the Qualcomm QCA Bluetooth driver. A missing sanity check can allow kernel slab memory data to be exposed during firmware selection. Business urgency depends on whether affected Linux kernels and QCA Bluetooth support exist in your fleet.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency from the available evidence. Prioritize patching where Linux systems use QCA Bluetooth support, especially managed endpoints or embedded devices that remain on affected kernel branches.
Technical view
The Linux kernel Bluetooth qca code lacked a sanity check while fetching the board ID. The CVE states this could leak slab data when later requesting firmware. The source bundle lists Linux kernel versions including 6.7, 6.8.10, and 6.9 as affected, with stable kernel fix commits referenced.
Likely exposure
Likely exposure is Linux systems using affected kernel builds with the Bluetooth QCA driver path. The bundle does not identify specific distributions, appliances, cloud images, or hardware models beyond Linux and the QCA Bluetooth code path.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. It describes an information leak, not code execution or privilege escalation. Practical exploitability and attacker proximity requirements are not established in the provided sources.
Researcher notes
Evidence is limited to the CVE description and stable kernel commit references. No CVSS, CWE, exploit narrative, distribution advisory, or KEV listing is provided. Avoid assuming exploitability beyond the stated slab information leak during firmware request handling.
Mitigation direction
Update to a kernel or distro package that includes the cited stable fixes.
Check Linux distribution and device-vendor advisories for fixed package versions.
Prioritize systems with Bluetooth enabled and QCA Bluetooth hardware or driver usage.
Track CVE-2024-36033 until your vendor confirms remediation status.
Validation and detection
Inventory Linux kernel versions across affected endpoints and embedded systems.
Identify systems using the Bluetooth QCA driver path.
Compare kernel source or package changelogs against the cited stable fix commits.
Confirm vendor advisories map the CVE to installed package versions.
Regression-test Bluetooth functionality after kernel or firmware-related updates.
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-36033 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.