LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35851: Bluetooth: qca: fix NULL-deref on non-serdev suspend

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: fix NULL-deref on non-serdev suspend Qualcomm ROME controllers can be registered from the Bluetooth line discipline and in this case the HCI UART serdev pointer is NULL. Add the missing sanity check to prevent a NULL-pointer dereference when wakeup() is called for a non-serdev controller during suspend. Just return true for now to restore the original behaviour and address the crash with pre-6.2 kernels, which do not have commit e9b3e5b8c657 ("Bluetooth: hci_qca: only assign wakeup with serial port support") that causes the crash to happen already at setup() time.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-35851 is a Linux kernel Bluetooth driver bug that can crash affected systems during suspend when certain Qualcomm ROME Bluetooth controllers are registered without a serial-device pointer. The public record describes a NULL-pointer dereference, not data theft or remote code execution.

Executive priority

Treat this as a targeted reliability issue rather than a broad breach scenario. Patch through normal kernel maintenance, with higher priority for fleets where suspend stability affects user productivity, kiosks, embedded systems, or field devices.

Technical view

The flaw is in the Linux Bluetooth QCA path. For non-serdev Qualcomm ROME controllers, the HCI UART serdev pointer can be NULL. A missing sanity check allowed wakeup handling during suspend to dereference that NULL pointer. Kernel stable commits add the check and restore prior behavior.

Likely exposure

Exposure is likely limited to Linux systems using affected kernel builds with Qualcomm ROME Bluetooth controllers registered through the Bluetooth line discipline rather than serdev. The bundle does not identify specific distributions, devices, or package names.

Exploitation context

The source bundle does not show KEV listing, active exploitation, public exploit details, or remote attack evidence. The described impact is a crash path during suspend, so operational risk is primarily local availability and device reliability.

Researcher notes

Evidence is limited to the CVE record and Linux stable references. No CVSS, CWE, exploit status, distribution mapping, or complete affected-version rationale is provided in the bundle. Validate exposure against actual kernel source or vendor backport metadata.

Mitigation direction

  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • Prioritize laptops, embedded devices, and appliances using Qualcomm ROME Bluetooth hardware.
  • Check distribution advisories for backported fixes and supported package versions.
  • Use vendor guidance before disabling Bluetooth or suspend workflows as a workaround.

Validation and detection

  • Inventory Linux kernel versions across systems with Bluetooth hardware enabled.
  • Identify systems using Qualcomm ROME or QCA Bluetooth controllers.
  • Confirm installed kernels include the relevant upstream stable fix commits or vendor backports.
  • Review suspend or resume crash reports for Bluetooth QCA NULL dereference indicators.
Prepared
Confidence
medium
Sources
7

Public sources used

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-35851 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
6Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc1a74160eaf1ac218733b371158432b52601beff, c1a74160eaf1ac218733b371158432b52601beff, c1a74160eaf1ac218733b371158432b52601beff, c1a74160eaf1ac218733b371158432b52601beff, c1a74160eaf1ac218733b371158432b52601beffunaffected
LinuxLinux5.13, 0, 5.15.158, 6.1.90, 6.6.30, 6.8.9, 6.9affected
Weakness

CWE details

No CWE listed

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