LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42137: Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot Commit 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed serdev") will cause below regression issue: BT can't be enabled after below steps: cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure if property enable-gpios is not configured within DT|ACPI for QCA6390. The commit is to fix a use-after-free issue within qca_serdev_shutdown() by adding condition to avoid the serdev is flushed or wrote after closed but also introduces this regression issue regarding above steps since the VSC is not sent to reset controller during warm reboot. Fixed by sending the VSC to reset controller within qca_serdev_shutdown() once BT was ever enabled, and the use-after-free issue is also fixed by this change since the serdev is still opened before it is flushed or wrote. Verified by the reported machine Dell XPS 13 9310 laptop over below two kernel commits: commit e00fc2700a3f ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of bluetooth-next tree. commit b23d98d46d28 ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of linus mainline tree.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Bluetooth reliability on systems using Qualcomm QCA6390 hardware. After a warm reboot, Bluetooth may fail to enable when a specific firmware reset path is missed. The public record describes an availability and device-function regression, not data theft or remote system compromise.

Executive priority

Handle through normal kernel patch management unless Bluetooth availability is business-critical on affected laptops. There is no cited evidence of exploitation or broader compromise impact, but affected endpoints may experience user disruption after reboot.

Technical view

The qca Bluetooth serdev shutdown path changed to avoid use-after-free behavior but regressed QCA6390 warm reboot handling when enable-gpios is absent from DT or ACPI. The fix sends the vendor-specific controller reset command while serdev is still open after Bluetooth was enabled.

Likely exposure

Exposure is likely limited to Linux systems with QCA6390 Bluetooth using the qca/hci_qca path, especially laptops like the reported Dell XPS 13 9310 configuration. General servers without this Bluetooth hardware are unlikely to be affected.

Exploitation context

The source bundle does not show active exploitation, public exploit use, or KEV listing. The described impact is Bluetooth enable failure after a specific reboot and enable/disable sequence, which points to local availability impact rather than attacker-driven compromise.

Researcher notes

Evidence is specific to Linux Bluetooth qca serdev behavior and QCA6390. The record lists multiple stable commit references and Debian LTS coverage, but no CVSS, CWE, exploitability detail, or attacker preconditions beyond the functional regression scenario.

Mitigation direction

  • Update to a kernel or distribution package containing the listed stable fixes.
  • Apply Debian LTS or vendor kernel updates where applicable.
  • Prioritize devices that depend on Bluetooth for business workflows.
  • If no package is available, check vendor guidance before using local kernel patches.

Validation and detection

  • Inventory Linux endpoints for Qualcomm QCA6390 Bluetooth hardware.
  • Compare running kernel builds against vendor fixed package advisories.
  • Confirm affected device trees or ACPI lack enable-gpios where relevant.
  • Test Bluetooth enablement after warm reboot on representative affected hardware.
Prepared
Confidence
medium
Sources
9

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-42137 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
8Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe84ec6e25df9bb0968599e92eacedaf3a0a5b587, 908d1742b6e694e84ead5c62e4b7c1bfbb8b46a3, ea3ebda47dd56f6e1c62f2e0e1b6e1b0a973e447, 272970be3dabd24cbe50e393ffee8f04aec3b9a8, 272970be3dabd24cbe50e393ffee8f04aec3b9a8, 272970be3dabd24cbe50e393ffee8f04aec3b9a8, 5.10.165, 5.15.90, 6.1.8unaffected
LinuxLinux6.2, 0, 5.10.222, 5.15.163, 6.1.98, 6.6.39, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

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