Skip to main content
VulnerabilityPublished Updated

CVE-2026-98809: Linux kernel · Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e8ba8c9c74d1035042cdf6cb5adf8f59b9b1271c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e8ba8c9c74d1035042cdf6cb5adf8f59b9b1271c, b11acfcb5925ed27fae692b27931a1ac732677fb, b1f24c1ab52345e810c42a1a81286cb5a7c92252 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 008ee9eb8a11bcabf12c91771dd4f470b082bd44, < e8ba8c9c74d1035042cdf6cb5adf8f59b9b1271c
Fixed in
  • e8ba8c9c74d1035042cdf6cb5adf8f59b9b1271c
LinuxLinuxAffected
  • ≥ 008ee9eb8a11bcabf12c91771dd4f470b082bd44, < b11acfcb5925ed27fae692b27931a1ac732677fb
Fixed in
  • b11acfcb5925ed27fae692b27931a1ac732677fb
LinuxLinuxAffected
  • ≥ 008ee9eb8a11bcabf12c91771dd4f470b082bd44, < b1f24c1ab52345e810c42a1a81286cb5a7c92252
Fixed in
  • b1f24c1ab52345e810c42a1a81286cb5a7c92252
LinuxLinuxAffected
  • ≥ 008ee9eb8a11bcabf12c91771dd4f470b082bd44, < 143bde97c4101ae68eb656c87e620c45b07a3090
Fixed in
  • 143bde97c4101ae68eb656c87e620c45b07a3090
LinuxLinuxAffected
  • ≥ 008ee9eb8a11bcabf12c91771dd4f470b082bd44, < 7f16443a30f4e86d84ae4faf057d333b41ddb757
Fixed in
  • 7f16443a30f4e86d84ae4faf057d333b41ddb757
LinuxLinuxAffected
  • =5.17
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister hci_unregister_dev() disables cmd_work and cmd_timer, then calls hci_cmd_sync_clear(), whose cancel_work_sync() waits for hci_cmd_sync_work() to return. That worker dequeues and runs every entry on cmd_sync_work_list. With cmd_work disabled nothing reaches the controller, so each queued HCI command waits the full HCI_CMD_TIMEOUT (2s). The backlog has no bound. Userspace can keep queuing MGMT commands such as MGMT_OP_GET_CLOCK_INFO against a controller that doesn't answer. Closing /dev/vhci then blocks in vhci_release() for backlog * 2s: INFO: task syz-executor:5749 blocked for more than 143 seconds. cancel_work_sync hci_cmd_sync_clear hci_unregister_dev vhci_release In a local reproduction the backlog held more than 5000 entries, which comes to hours of hang. Stop the worker from taking new entries once HCI_UNREGISTER is set, and wake any request still waiting with -ENODEV before cancelling the work. The entries left over are destroyed with -ECANCELED by the existing sweep in hci_cmd_sync_clear(). They stay on the list until the work has stopped, so hci_cmd_sync_dequeue() and friends still see them. A callback already running may still issue another command, which delays unregister by at most one timeout per remaining command, not by the whole backlog.

References

Community reviews

Loading reviews…