CVE-2026-93247Bluetooth: mgmt: fix 'hdev->discovery.uuids' NULL dereference
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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() allocation in start_service_discovery(), otherwise uuids is NULL, because kmemdup failed, but uuid_count is already assigned to non zero value. The following panic happens: [ ] ------------[ cut here ]------------ [ ] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ ] Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP [ ] CPU: 0 PID: 15056 Comm: kworker/u9:2 [ ] Workqueue: hci0 hci_rx_work [ ] pstate: 10400009 (nzcV daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ ] pc : eir_has_uuids+0x2d8/0x590 [ ] lr : is_filter_match+0x258/0x320 ... [ ] Call trace: [ ] eir_has_uuids+0x2d8/0x590 [ ] is_filter_match+0x258/0x320 [ ] mgmt_device_found+0x5b0/0xafc [ ] process_adv_report.part.0+0x8c8/0xf14 [ ] hci_le_adv_report_evt+0x338/0x3f0 [ ] hci_le_meta_evt+0x1f0/0x4c8 [ ] hci_event_packet+0x440/0xc9c [ ] hci_rx_work+0x44c/0xaf8 [ ] process_one_work+0x54c/0x103c [ ] worker_thread+0x6c4/0x10c4 [ ] kthread+0x274/0x2ec [ ] ret_from_fork+0x10/0x20 [ ] Code: 14000004 91004021 eb14003f 54000180 (f9400024) [ ] ---[ end trace 0000000000000000 ]---
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 25 days later
· 25 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 86f3dcd1f331cfd4fd7ec88906955134ec51afbe – < f02c01ccd12cb2b8a290077d4c90f29a6e109b16
- affected 7ce9bb0b95fc280e9212b8922590c492ca1d9c39 – < bbd262d2d750b67b15a5e1008d3848309c87e7a7
- affected 16852eccbdfaf41a666705e3f8be55cf2864c5ca – < 18fda026a13c5abd6c1e0dfd3549f490b73378fb
- affected 2935e556850e9c94d7a00adf14d3cd7fe406ac03 – < c3f63610bceaa182e4683b23cc47baf36b5f1496
- affected 2935e556850e9c94d7a00adf14d3cd7fe406ac03 – < ee2135a14fb2a3e176149122764d293f0796b1eb
- affected 2935e556850e9c94d7a00adf14d3cd7fe406ac03 – < 59eecbe2f2f38d8f3e1104bd11da97f9a2c58998
- affected a351ff6b8ecca4229afaa0d98042bead8de64799
- affected f8069f34c4c976786ded97498012225af87435d7
- affected 6.1.159 – < 6.1.188
- affected 6.6.117 – < 6.6.157
- affected 6.12.42 – < 6.12.110
- affected 6.15.10 – < 6.16
- affected 6.16.1 – < 6.17
- affected 6.17
- unaffected < 6.17
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/f02c01ccd12cb2b8a290077d4c90f29a6e109b16 (opens in a new tab)
- https://git.kernel.org/stable/c/bbd262d2d750b67b15a5e1008d3848309c87e7a7 (opens in a new tab)
- https://git.kernel.org/stable/c/18fda026a13c5abd6c1e0dfd3549f490b73378fb (opens in a new tab)
- https://git.kernel.org/stable/c/c3f63610bceaa182e4683b23cc47baf36b5f1496 (opens in a new tab)
- https://git.kernel.org/stable/c/ee2135a14fb2a3e176149122764d293f0796b1eb (opens in a new tab)
- https://git.kernel.org/stable/c/59eecbe2f2f38d8f3e1104bd11da97f9a2c58998 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86257 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93247)Record last updated .