CVE-2026-93247: Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference
Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.157.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
What conditions are required to trigger the crash?
The issue requires a race between Bluetooth discovery-state operations that leaves uuid_count nonzero while the uuids pointer is NULL. A device-found event can then reach the UUID filter matching path and dereference the NULL pointer.
What is the practical impact of successful triggering?
The described outcome is a NULL pointer dereference in the Linux kernel's Bluetooth management discovery handling. The provided information supports a crash or denial-of-service impact; it does not describe code execution or data disclosure.
What changes does the fix make?
The fix protects reads and writes of the discovery uuid_count and uuids pair with discovery.lock, preventing consumers from observing inconsistent state. It also assigns uuid_count only after the UUID array allocation succeeds.