CVE-2026-68085High· 8.0▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled HCI_UART_SENDING bit in tx_state means write_work is pending and blocks queueing it again. Cur…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 44 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled
HCI_UART_SENDING bit in tx_state means write_work is pending and blocks queueing it again. Currently this bit is not cleared when canceling the work in hci_uart_close(), which blocks future writes when device is reopened later if write_work was pending.
Fix by clearing HCI_UART_SENDING when canceling the work.
Also make clearing of tx_skb safe by using disable_work_sync + enable_work instead of just cancel_work_sync. hci_uart_flush() purges the proto tx queue so we can cancel the pending write_work there, instead of doing it just in hci_uart_close(). Re-enable and possibly requeue the work after queue flush.
Linux >= 81c7a3c22a0f2808cf4ae0b4908f59763b23606d < d52446b3e735cfdbdc2a58342163803bc2e64249Linux >= 192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894 < b9dd39cf1667e378b25a082ca796d495d578c5d3Linux >= c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b < 714d861d35d937f23375a4517569b13917bbbe51Linux >= c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b < 1b0d946d6f08bd39211385bc703a440911b41e46Linux 78aad93e938f013d9272fe0ee168f27883afa95cLinux e2d19969c8d9198ecc3090bcd5312ecd503a3339Linux c85cff648a2bc92322912db5f1727ad05afae7b6Linux 9d20d48be2c4a071fb015eb09bda2cecd25daf34Linux 7338031946bd06f6dff149e67b60c4cd083bfea8Linux >= 6.12.92 < 6.12.96Linux >= 6.18.34 < 6.18.39Linux >= 5.10.258 < 5.11Linux >= 5.15.209 < 5.16Linux >= 6.1.175 < 6.2Linux >= 6.6.142 < 6.7Linux >= 7.0.11 < 7.1Linux 7.1Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99100Nonewifi: p54: validate firmware record lengths
CVE-2024-38564High· 7.8bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
CVE-2026-99092Noneriscv: patch: fix handling of bpf-jit execmem addresses
CVE-2026-99089NoneASoC: samsung: i2s: enable op_clk in probe to balance runtime PM
CVE-2026-99093Nonemm: don't schedule deferred kernel page table freeing while booting
CVE-2026-99088Nonenet: openvswitch: validate transport header presence in set_ipv6_addr