Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98297Bluetooth: hci_core: Fix queuing tx_work after workqueue is drained

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Fix queuing tx_work after workqueue is drained hci_send_acl(), hci_send_sco() and hci_send_iso() queue hdev->tx_work unconditionally. They can run from the L2CAP/SCO/ISO socket send path while hci_dev_close_sync() is draining hdev->workqueue (HCIDEVDOWN racing with a socket write). Since that queue_work() is not chained work from the tx_work worker itself, __queue_work() sees the queue marked __WQ_DRAINING, warns "cannot queue %ps on wq %s", and drops the work: WARNING: CPU: 1 PID: 5985 at kernel/workqueue.c:2352 __queue_work Call Trace: queue_work_on l2cap_chan_send l2cap_sock_sendmsg ... hci_dev_close_sync() already sets HCI_CMD_DRAIN_WORKQUEUE before draining, but only hci_cmd_work() and handle_cmd_cnt_and_timer() check it before queuing. Route the tx_work producers through the same guard via a shared hci_sched_tx() helper.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ccf07dfb9d7d1e2c7a1eeb782f90d9b614ebba9c – < 9943b4c70ad972f368705da8605054f865b08dad
    • affected 7b81c1378b79c3143ca3fdb3d18ac0f01cbabb21 – < 8010212197d4a3ee714f78ed77048d0b712ff925
    • affected 9cebe4680bb9a72f80c6541eb24af06db7a1fbc9 – < ab0678a0701ac4de499428dc1b321659bb74d272
    • affected 47330cc875b36a1cf7b3543cb2cf90a7c603ce0e – < e220c1242a643d97102a79f09b7ef3aa31276961
    • affected 525daaea459fc215f432de1b8debbd9144bf97b0 – < cbb325bc150e8c0dbce004ac0e5516bcffc0de31
    • affected 525daaea459fc215f432de1b8debbd9144bf97b0 – < 6610c6fe4b8936c232048e6049bf77c70a6f759c
    • affected 60bceb9a4c693e68cc90ba4b2dfb9e000e8638ff
    • affected 6.12.93 – < 6.12.112
    • affected 6.18.35 – < 6.18.54
    • affected 7.0.12 – < 7.1
  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98297 badge
[![CVE-2026-98297](https://cveledger.app/badge/CVE-2026-98297.svg)](https://cveledger.app/cve/CVE-2026-98297)

Record last updated .