Skip to main content
Vulnerability Database/CVE-2026-97908

CVE-2026-97908: Linux Kernel Bluetooth Use-After-Free Flaw

CVE-2026-97908 is a use-after-free vulnerability in the Linux kernel Bluetooth subsystem that can cause freed memory access during RPMsg endpoint teardown. This article covers technical details, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97908 Overview

CVE-2026-97908 is a use-after-free vulnerability in the Linux kernel's btqcomsmd Bluetooth driver, which handles Qualcomm Shared Memory Driver (SMD) communication with WCNSS wireless subsystems. The flaw stems from an incorrect teardown ordering: the driver frees the hci_dev structure before destroying the Remote Processor Messaging (RPMsg) endpoints that reference it through callback private data. If WCNSS delivers data during that window, the receive callback dereferences an already freed hci_dev and passes it to the Bluetooth core.

Critical Impact

A race between RPMsg receive callbacks and HCI device teardown can trigger a use-after-free on hci_dev, leading to kernel memory corruption or denial of service on affected Qualcomm-based Linux systems.

Affected Products

  • Linux kernel versions containing the drivers/bluetooth/btqcomsmd.c driver prior to the fix
  • Qualcomm WCNSS-based platforms using the btqcomsmd Bluetooth transport driver
  • Downstream distributions shipping affected stable kernel branches

Discovery Timeline

  • 2026-09-25 - CVE-2026-97908 published to NVD
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-97908

Vulnerability Analysis

The btqcomsmd driver registers two RPMsg endpoints, one for HCI commands and one for Asynchronous Connection-Less (ACL) data. Each endpoint stores a struct btqcomsmd pointer as its callback private data. The receive callbacks dereference btq->hdev without acquiring an hci_dev reference, assuming the parent device remains valid for the lifetime of the endpoint.

In both the hci_register_dev() error path and the driver remove path, the existing teardown order calls hci_free_dev() before rpmsg_destroy_ept(). This leaves the endpoints active with a dangling pointer to freed Bluetooth core memory. If the WCNSS firmware delivers a command response or ACL packet during that window, the callback executes against released memory [CWE-416].

Root Cause

The root cause is incorrect object lifetime management across two subsystems. The RPMsg endpoint lifetime is not bound to the hci_dev lifetime, and no reference counting protects the shared pointer. The driver author assumed teardown would be quiescent, but qcom_smd channels can continue delivering data until the endpoint is explicitly destroyed.

Attack Vector

Exploitation requires timing-sensitive conditions during driver teardown or registration failure. For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock, while the receive path holds the same lock during callback invocation. The fix destroys the command and ACL endpoints before hci_free_dev(), which both prevents new callbacks and serializes against any callback already running. The remove path retains hci_unregister_dev() first so the HCI core stops issuing operations before transport endpoints shut down. The registration-error cleanup path returns directly after freeing hci_dev to avoid double-destroying endpoints via fall-through to partial-construction labels.

Technical details are available in the upstream commits: commit 2d016208, commit 2dcc2240, commit 962dcc1d, and commit f5a427b1.

Detection Methods for CVE-2026-97908

Indicators of Compromise

  • Kernel panic or oops referencing btqcomsmd_cmd_callback or btqcomsmd_acl_callback with freed-slab access patterns.
  • KASAN use-after-free reports naming hci_dev or btqcomsmd structures during Bluetooth driver unload or probe failure.
  • Unexpected Bluetooth stack crashes correlated with WCNSS firmware restart events or module reload cycles.

Detection Strategies

  • Enable CONFIG_KASAN on test and staging kernels to surface use-after-free access on hci_dev during stress testing of Bluetooth probe and remove paths.
  • Audit running kernels against the upstream fix commits to confirm whether the teardown reordering is present in drivers/bluetooth/btqcomsmd.c.
  • Inspect dmesg and persistent kernel logs for repeated Bluetooth transport failures preceding system instability.

Monitoring Recommendations

  • Collect kernel crash dumps and pstore logs centrally to identify use-after-free signatures across Qualcomm-based fleet devices.
  • Monitor module load and unload events for btqcomsmd to correlate with crash telemetry.
  • Track distribution kernel package versions to confirm patched builds are deployed on affected hardware.

How to Mitigate CVE-2026-97908

Immediate Actions Required

  • Apply the upstream Linux kernel patches that reorder RPMsg endpoint destruction before hci_free_dev() in btqcomsmd.
  • Update to a distribution kernel that incorporates the fix commits referenced in the NVD advisory.
  • On systems that cannot be patched immediately, avoid repeated reloads of the btqcomsmd module and limit WCNSS firmware restart scenarios.

Patch Information

The fix destroys the command and ACL RPMsg endpoints before calling hci_free_dev() in both the hci_register_dev() error path and the driver remove path. The remove path keeps hci_unregister_dev() first so the HCI core stops issuing operations before the transport is torn down. The registration-error path returns immediately after freeing hci_dev to prevent double-destroy of endpoints. The patches are available at commit 2d016208, commit 2dcc2240, commit 962dcc1d, and commit f5a427b1.

Workarounds

  • Disable the btqcomsmd module on affected devices where Bluetooth functionality is not required until the patched kernel is installed.
  • Restrict physical and local access to Qualcomm-based devices to reduce opportunities for triggering driver teardown scenarios.
  • Maintain stable WCNSS firmware to minimize unexpected restarts that increase race-window exposure.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.