CVE-2026-98297
Last modified
CVE-2026-98297 is a vulnerability of currently unknown severity. 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).
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9cebe4680bb9a72f80c6541eb24af06db7a1fbc9, < ab0678a0701ac4de499428dc1b321659bb74d272; >= 47330cc875b36a1cf7b3543cb2cf90a7c603ce0e, < e220c1242a643d97102a79f09b7ef3aa31276961; >= 525daaea459fc215f432de1b8debbd9144bf97b0, < cbb325bc150e8c0dbce004ac0e5516bcffc0de31; >= 525daaea459fc215f432de1b8debbd9144bf97b0, < 6610c6fe4b8936c232048e6049bf77c70a6f759c; 60bceb9a4c693e68cc90ba4b2dfb9e000e8638ff; >= 6.12.93, < 6.12.112; >= 6.18.35, < 6.18.54; >= 7.0.12, < 7.1 |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98297?
How severe is CVE-2026-98297?
How do I fix CVE-2026-98297?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98291In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98292In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98293In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98294In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98295In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98296In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98298In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98299In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9830The bookingpress-appointment-booking-pro WordPress plugin be…8.2
- CVE-2026-98300In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98301In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98302In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98297?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
