Live › vulnerability › CVE-2026-98456
Go to dashboardA race in the Linux kernel Bluetooth management interface can cause an out-of-bounds write when listing unconfigured controllers. The sources do not say what an attacker gets beyond memory corruption in the kernel.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with Bluetooth support and the management interface in use, typically desktops, laptops and devices with Bluetooth controllers. The sources do not say whether headless servers without Bluetooth hardware are affected or whether a local user can trigger it.
No product ranges from the sources yet.
uname -r to see the running kernel versionEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: mgmt: fix race in read_unconf_index_list()
read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.
hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].
Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.
This page as .md · .json · in your agent: get_signal("CVE-2026-98456")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.