CVE-2026-93247

Kelemahan

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference 'uuid_count' member of struct 'discovery_state' is assigned and read without any locks, so there is a chance of situation when uuid_count != 0, but uuids is NULL and there will be NULL pointer dereference. Possible race: 'hci_update_passive_scan_sync' 'hci_discovery_filter_clear' hdev->discovery.uuid_count = 0; <----------------------preempted-----------------------------> 'start_service_discovery' // Set uuid_count to value != 0 hdev->discovery.uuid_count = uuid_count; hdev->discovery.uuids = kmemdup(...); <----------------------preempted-----------------------------> spin_lock(&hdev->discovery.lock); kfree(hdev->discovery.uuids); hdev->discovery.uuids = NULL; spin_unlock(&hdev->discovery.lock); Now uuids == NULL and uuid_count != 0. So 'mgmt_device_found' -> 'is_filter_match' -> 'eir_has_uuids' receives non consistent discovery state, where NULL dereference of uuids happens. To fix it let's add discovery.lock around every read/write of uuid_count, uuids pair of struct members. It is also important to assign uuid_count value only after success kmemdup()

Referensi

• https://git.kernel.org/stable/c/18fda026a13c5abd6c1e0dfd3549f490b73378fb
• https://git.kernel.org/stable/c/59eecbe2f2f38d8f3e1104bd11da97f9a2c58998
• https://git.kernel.org/stable/c/bbd262d2d750b67b15a5e1008d3848309c87e7a7
• https://git.kernel.org/stable/c/c3f63610bceaa182e4683b23cc47baf36b5f1496
• https://git.kernel.org/stable/c/ee2135a14fb2a3e176149122764d293f0796b1eb
• https://git.kernel.org/stable/c/f02c01ccd12cb2b8a290077d4c90f29a6e109b16