Bluetooth: hci_core: Fix queuing tx_work after workqueue is drained
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.112, 6.18.54, 7.2.8
- CVEs
- CVE-2026-98297
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:45 UTC · Revision 1
Source evidence
Bluetooth: hci_core: Fix queuing tx_work after workqueue is drained
core-osv · Original sourcePublished 6 Oct 2026, 08:45 UTC
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.
osv:CVE-2026-98297
Kernel
Fixed versions: 6.12.112, 6.18.54, 7.2.8
Complete source record
{
"id": "be9c98943a2196abfb9170af15bda19fbf27cfa2caa13be7d53514b42b7da78b",
"url": "https://osv.dev/vulnerability/CVE-2026-98297",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bluetooth: hci_core: Fix queuing tx_work after workqueue is drained",
"summary": "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.",
"evidence": "osv:CVE-2026-98297",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.112",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.54",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98297",
"aliases": [
"CVE-2026-98297"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "ccf07dfb9d7d1e2c7a1eeb782f90d9b614ebba9c"
},
{
"fixed": "9943b4c70ad972f368705da8605054f865b08dad"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7b81c1378b79c3143ca3fdb3d18ac0f01cbabb21"
},
{
"fixed": "8010212197d4a3ee714f78ed77048d0b712ff925"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "9cebe4680bb9a72f80c6541eb24af06db7a1fbc9"
},
{
"fixed": "ab0678a0701ac4de499428dc1b321659bb74d272"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "47330cc875b36a1cf7b3543cb2cf90a7c603ce0e"
},
{
"fixed": "e220c1242a643d97102a79f09b7ef3aa31276961"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "525daaea459fc215f432de1b8debbd9144bf97b0"
},
{
"fixed": "cbb325bc150e8c0dbce004ac0e5516bcffc0de31"
},
{
"fixed": "6610c6fe4b8936c232048e6049bf77c70a6f759c"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.12.93"
},
{
"fixed": "6.12.112"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6.18.35"
},
{
"fixed": "6.18.54"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7.0.12"
},
{
"fixed": "7.1"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "60bceb9a4c693e68cc90ba4b2dfb9e000e8638ff"
}
]
}
],
"versions": [
"v6.12.111",
"v6.12.110",
"v6.12.109",
"v6.12.108",
"v6.12.107",
"v6.12.106",
"v6.12.105",
"v6.12.104",
"v6.12.103",
"v6.12.102",
"v6.12.101",
"v6.12.100",
"v6.12.99",
"v6.12.98",
"v6.12.97",
"v6.12.96",
"v6.12.95",
"v6.12.94",
"v6.12.93",
"v6.18.53",
"v6.18.52",
"v6.18.51",
"v6.18.50",
"v6.18.49",
"v6.18.48",
"v6.18.47",
"v6.18.46",
"v6.18.45",
"v6.18.44",
"v6.18.43",
"v6.18.42",
"v6.18.41",
"v6.18.40",
"v6.18.39",
"v6.18.38",
"v6.18.37",
"v6.18.36",
"v6.18.35",
"v7.0.14",
"v7.0.13",
"v7.0.12"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98297.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.12.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.54"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98297.json"
}
}
],
"modified": "2026-11-01T02:30:37.947677199Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/6610c6fe4b8936c232048e6049bf77c70a6f759c",
"https://git.kernel.org/stable/c/8010212197d4a3ee714f78ed77048d0b712ff925",
"https://git.kernel.org/stable/c/9943b4c70ad972f368705da8605054f865b08dad",
"https://git.kernel.org/stable/c/ab0678a0701ac4de499428dc1b321659bb74d272",
"https://git.kernel.org/stable/c/cbb325bc150e8c0dbce004ac0e5516bcffc0de31",
"https://git.kernel.org/stable/c/e220c1242a643d97102a79f09b7ef3aa31276961",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98297.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98297",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98297.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98297",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 489312,
"published_at": "2026-10-06T08:45:55.723+00:00"
}