{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93247 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93247 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93247 and fix it if it is affected.\n\nWhat it is: CVE-2026-93247 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93247 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93247/ (Markdown: https://insights.sbomify.com/CVE-2026-93247/index.md)","id":"CVE-2026-93247","markdown":"https://insights.sbomify.com/CVE-2026-93247/index.md","name":"CVE-2026-93247","record":{"aliases":["BELL-CVE-2026-93247","DEBIAN-CVE-2026-93247","GHSA-v2qr-f43f-h5vh","UBUNTU-CVE-2026-93247"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"none","summary":"A race condition in the Linux kernel Bluetooth subsystem causes a NULL pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: mgmt: fix 'hdev-\u003ediscovery.uuids' NULL dereference\n\n'uuid_count' member of struct 'discovery_state' is assigned and read\nwithout any locks, so there is a chance of situation when\nuuid_count != 0, but uuids is NULL and there will be NULL pointer\ndereference.\n\nPossible race:\n'hci_update_passive_scan_sync'\n  'hci_discovery_filter_clear'\n    hdev-\u003ediscovery.uuid_count = 0;\n      \u003c----------------------preempted-----------------------------\u003e\n                        'start_service_discovery'\n                          // Set uuid_count to value != 0\n                          hdev-\u003ediscovery.uuid_count = uuid_count;\n                          hdev-\u003ediscovery.uuids = kmemdup(...);\n      \u003c----------------------preempted-----------------------------\u003e\n    spin_lock(\u0026hdev-\u003ediscovery.lock);\n    kfree(hdev-\u003ediscovery.uuids);\n    hdev-\u003ediscovery.uuids = NULL;\n    spin_unlock(\u0026hdev-\u003ediscovery.lock);\n\nNow uuids == NULL and uuid_count != 0.\nSo 'mgmt_device_found' -\u003e 'is_filter_match' -\u003e 'eir_has_uuids' receives\nnon consistent discovery state, where NULL dereference of uuids happens.\n\nTo fix it let's add discovery.lock around every read/write of uuid_count,\nuuids pair of struct members. It is also important to assign uuid_count\nvalue only after success kmemdup() allocation in\nstart_service_discovery(), otherwise uuids is NULL, because kmemdup failed,\nbut uuid_count is already assigned to non zero value.\n\nThe following panic happens:\n\n[ ] ------------[ cut here ]------------\n[ ] Unable to handle kernel NULL pointer dereference at virtual\naddress 0000000000000000\n[ ] Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP\n[ ] CPU: 0 PID: 15056 Comm: kworker/u9:2\n[ ] Workqueue: hci0 hci_rx_work\n[ ] pstate: 10400009 (nzcV daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ ] pc : eir_has_uuids+0x2d8/0x590\n[ ] lr : is_filter_match+0x258/0x320\n...\n[ ] Call trace:\n[ ]  eir_has_uuids+0x2d8/0x590\n[ ]  is_filter_match+0x258/0x320\n[ ]  mgmt_device_found+0x5b0/0xafc\n[ ]  process_adv_report.part.0+0x8c8/0xf14\n[ ]  hci_le_adv_report_evt+0x338/0x3f0\n[ ]  hci_le_meta_evt+0x1f0/0x4c8\n[ ]  hci_event_packet+0x440/0xc9c\n[ ]  hci_rx_work+0x44c/0xaf8\n[ ]  process_one_work+0x54c/0x103c\n[ ]  worker_thread+0x6c4/0x10c4\n[ ]  kthread+0x274/0x2ec\n[ ]  ret_from_fork+0x10/0x20\n[ ] Code: 14000004 91004021 eb14003f 54000180 (f9400024)\n[ ] ---[ end trace 0000000000000000 ]---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Bluetooth: mgmt: fix 'hdev-\u003ediscovery.uuids' NULL dereference","id":"CVE-2026-93247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"drm/xe: don't WARN on kernel job timeout when device already wedged","id":"CVE-2026-93248"},"packages":[],"prev":{"headline":"octeontx2-af: fix out-of-bounds read setting MSI-X irq affinity","id":"CVE-2026-93246"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Bluetooth subsystem causes a NULL pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-93247/"}