CVE-2026-46275 is a Linux kernel vulnerability in the Bluetooth hci_uart subsystem caused by incorrect synchronization and object lifecycle handling in close and initialization paths. The bug affects teardown of the hci_uart context (hu) and associated workqueues (init_ready and write_work). If a TTY hangup occurs before setup completes, hci_uart_tty_close() may skip cancelling or flushing queued work because teardown was gated on the HCI_UART_PROTO_READY flag, then free the hu structure. Deferred work can later execute and dereference the freed hu, resulting in a use-after-free. Additional flaws include a race between hci_uart_flush() and write_work that can double-free hu->tx_skb, incorrect ordering where hci_free_dev(hdev) is called before hu->proto->close(hu) allowing vendor protocol close callbacks to access a freed hu->hdev, and initialization error-path locking issues where PROTO_READY is cleared without the required write lock while hci_uart_tty_receive() accesses hu->hdev outside the read-side critical section. The combined issues can trigger use-after-free, null pointer dereference, and memory corruption conditions in kernel space.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
HCI_UART_PROTO_READY before cancelling write_work, using cancel_work_sync() to flush pending work safely, moving hu->proto->close(hu) before hci_free_dev(hdev) in close and error paths, and correcting locking around PROTO_READY and hu->hdev access in receive and initialization error paths. On Debian stable (trixie), upgrade the linux package to version 6.12.94-1 or later fixed package provided by Debian.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.