{"api_version":"1","generated_at":"2026-09-27T14:17:56+00:00","cve":"CVE-2026-98109","urls":{"html":"https://cve.report/CVE-2026-98109","api":"https://cve.report/api/cve/CVE-2026-98109.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98109","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98109"},"summary":{"title":"Bluetooth: hci_core: Fix race condition during device registration","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix race condition during device registration\n\nIn hci_register_dev(), the power_on work item is queued to\nhdev->req_workqueue before initializing hdev->adv_monitors_idr and\nregistering the MSFT extension via msft_register(). For devices marked with\nquirks such as HCI_QUIRK_RAW_DEVICE, the HCI_UNCONFIGURED flag is set on\nthe device. When the power_on work item runs concurrently on another CPU,\nhci_power_on() detects that the device is unconfigured and immediately\ninvokes hci_dev_do_close(), which calls msft_do_close().\n\nConcurrently, msft_register() allocates the msft structure and exposes it\nto hdev->msft_data prior to calling mutex_init(&msft->filter_lock). If\nmsft_do_close() executes while hdev->msft_data is already assigned but the\nmutex has not yet been initialized, mutex_lock(&msft->filter_lock) operates\non an uninitialized mutex, triggering a DEBUG_LOCKS warning:\n\nDEBUG_LOCKS_WARN_ON(lock->magic != lock)\nWARNING: kernel/locking/mutex.c:625 at __mutex_lock_common\nkernel/locking/mutex.c:625 [inline]\nWARNING: kernel/locking/mutex.c:625 at __mutex_lock+0x12d8/0x1550\nkernel/locking/mutex.c:821\n...\nCall Trace:\n <TASK>\n msft_do_close+0x308/0x7b0 net/bluetooth/msft.c:693\n hci_dev_close_sync+0x86b/0x10a0 net/bluetooth/hci_sync.c:5522\n hci_dev_do_close net/bluetooth/hci_core.c:499 [inline]\n hci_power_on+0x32c/0x750 net/bluetooth/hci_core.c:937\n process_one_work kernel/workqueue.c:3322 [inline]\n process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405\n worker_thread+0x92d/0xe10 kernel/workqueue.c:3486\n kthread+0x388/0x470 kernel/kthread.c:436\n ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n </TASK>\n\nFix this by moving the queue_work() call in hci_register_dev() to after\nidr_init(&hdev->adv_monitors_idr) and msft_register(hdev) so that device\nstructures and extensions are fully initialized before asynchronous tasks\ncan access them. Additionally, assign hdev->msft_data in msft_register()\nonly after mutex_init(&msft->filter_lock) has completed.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:41","updated_at":"2026-09-25 11:17:41"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18","name":"https://git.kernel.org/stable/c/57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d427b1c71d9798083e954d3c13469dc0a2305868","name":"https://git.kernel.org/stable/c/d427b1c71d9798083e954d3c13469dc0a2305868","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a11ebe8dc0333fb870bbbb656b34690e87ee3f98","name":"https://git.kernel.org/stable/c/a11ebe8dc0333fb870bbbb656b34690e87ee3f98","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b1faf348c29e6f8302ec7769cbf1c1ef05be014f","name":"https://git.kernel.org/stable/c/b1faf348c29e6f8302ec7769cbf1c1ef05be014f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98109","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98109","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e14606d8f38ea52a38c27692a9c1513c987a5da b1faf348c29e6f8302ec7769cbf1c1ef05be014f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e14606d8f38ea52a38c27692a9c1513c987a5da a11ebe8dc0333fb870bbbb656b34690e87ee3f98 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e14606d8f38ea52a38c27692a9c1513c987a5da d427b1c71d9798083e954d3c13469dc0a2305868 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9e14606d8f38ea52a38c27692a9c1513c987a5da 57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f9965f7f38c90449a5fb26edb8a7d22b1dcf0283 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 80fe27811c56ecd3896c3d511ab8298146071d98 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.4.16 6.5 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.5.3 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"98109","cve":"CVE-2026-98109","epss":"0.001680000","percentile":"0.054080000","score_date":"2026-09-26","updated_at":"2026-09-27 00:04:19"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/bluetooth/hci_core.c","net/bluetooth/msft.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"b1faf348c29e6f8302ec7769cbf1c1ef05be014f","status":"affected","version":"9e14606d8f38ea52a38c27692a9c1513c987a5da","versionType":"git"},{"lessThan":"a11ebe8dc0333fb870bbbb656b34690e87ee3f98","status":"affected","version":"9e14606d8f38ea52a38c27692a9c1513c987a5da","versionType":"git"},{"lessThan":"d427b1c71d9798083e954d3c13469dc0a2305868","status":"affected","version":"9e14606d8f38ea52a38c27692a9c1513c987a5da","versionType":"git"},{"lessThan":"57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18","status":"affected","version":"9e14606d8f38ea52a38c27692a9c1513c987a5da","versionType":"git"},{"status":"affected","version":"f9965f7f38c90449a5fb26edb8a7d22b1dcf0283","versionType":"git"},{"status":"affected","version":"80fe27811c56ecd3896c3d511ab8298146071d98","versionType":"git"},{"lessThan":"6.5","status":"affected","version":"6.4.16","versionType":"semver"},{"lessThan":"6.6","status":"affected","version":"6.5.3","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/bluetooth/hci_core.c","net/bluetooth/msft.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.4.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.5.3","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix race condition during device registration\n\nIn hci_register_dev(), the power_on work item is queued to\nhdev->req_workqueue before initializing hdev->adv_monitors_idr and\nregistering the MSFT extension via msft_register(). For devices marked with\nquirks such as HCI_QUIRK_RAW_DEVICE, the HCI_UNCONFIGURED flag is set on\nthe device. When the power_on work item runs concurrently on another CPU,\nhci_power_on() detects that the device is unconfigured and immediately\ninvokes hci_dev_do_close(), which calls msft_do_close().\n\nConcurrently, msft_register() allocates the msft structure and exposes it\nto hdev->msft_data prior to calling mutex_init(&msft->filter_lock). If\nmsft_do_close() executes while hdev->msft_data is already assigned but the\nmutex has not yet been initialized, mutex_lock(&msft->filter_lock) operates\non an uninitialized mutex, triggering a DEBUG_LOCKS warning:\n\nDEBUG_LOCKS_WARN_ON(lock->magic != lock)\nWARNING: kernel/locking/mutex.c:625 at __mutex_lock_common\nkernel/locking/mutex.c:625 [inline]\nWARNING: kernel/locking/mutex.c:625 at __mutex_lock+0x12d8/0x1550\nkernel/locking/mutex.c:821\n...\nCall Trace:\n <TASK>\n msft_do_close+0x308/0x7b0 net/bluetooth/msft.c:693\n hci_dev_close_sync+0x86b/0x10a0 net/bluetooth/hci_sync.c:5522\n hci_dev_do_close net/bluetooth/hci_core.c:499 [inline]\n hci_power_on+0x32c/0x750 net/bluetooth/hci_core.c:937\n process_one_work kernel/workqueue.c:3322 [inline]\n process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405\n worker_thread+0x92d/0xe10 kernel/workqueue.c:3486\n kthread+0x388/0x470 kernel/kthread.c:436\n ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n </TASK>\n\nFix this by moving the queue_work() call in hci_register_dev() to after\nidr_init(&hdev->adv_monitors_idr) and msft_register(hdev) so that device\nstructures and extensions are fully initialized before asynchronous tasks\ncan access them. Additionally, assign hdev->msft_data in msft_register()\nonly after mutex_init(&msft->filter_lock) has completed."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:35:57.537Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/b1faf348c29e6f8302ec7769cbf1c1ef05be014f"},{"url":"https://git.kernel.org/stable/c/a11ebe8dc0333fb870bbbb656b34690e87ee3f98"},{"url":"https://git.kernel.org/stable/c/d427b1c71d9798083e954d3c13469dc0a2305868"},{"url":"https://git.kernel.org/stable/c/57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18"}],"title":"Bluetooth: hci_core: Fix race condition during device registration","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98109","datePublished":"2026-09-25T10:35:57.537Z","dateReserved":"2026-09-25T10:25:14.316Z","dateUpdated":"2026-09-25T10:35:57.537Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:41","lastModifiedDate":"2026-09-25 11:17:41","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98109","Ordinal":"1","Title":"Bluetooth: hci_core: Fix race condition during device registrati","CVE":"CVE-2026-98109","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98109","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Fix race condition during device registration\n\nIn hci_register_dev(), the power_on work item is queued to\nhdev->req_workqueue before initializing hdev->adv_monitors_idr and\nregistering the MSFT extension via msft_register(). For devices marked with\nquirks such as HCI_QUIRK_RAW_DEVICE, the HCI_UNCONFIGURED flag is set on\nthe device. When the power_on work item runs concurrently on another CPU,\nhci_power_on() detects that the device is unconfigured and immediately\ninvokes hci_dev_do_close(), which calls msft_do_close().\n\nConcurrently, msft_register() allocates the msft structure and exposes it\nto hdev->msft_data prior to calling mutex_init(&msft->filter_lock). If\nmsft_do_close() executes while hdev->msft_data is already assigned but the\nmutex has not yet been initialized, mutex_lock(&msft->filter_lock) operates\non an uninitialized mutex, triggering a DEBUG_LOCKS warning:\n\nDEBUG_LOCKS_WARN_ON(lock->magic != lock)\nWARNING: kernel/locking/mutex.c:625 at __mutex_lock_common\nkernel/locking/mutex.c:625 [inline]\nWARNING: kernel/locking/mutex.c:625 at __mutex_lock+0x12d8/0x1550\nkernel/locking/mutex.c:821\n...\nCall Trace:\n <TASK>\n msft_do_close+0x308/0x7b0 net/bluetooth/msft.c:693\n hci_dev_close_sync+0x86b/0x10a0 net/bluetooth/hci_sync.c:5522\n hci_dev_do_close net/bluetooth/hci_core.c:499 [inline]\n hci_power_on+0x32c/0x750 net/bluetooth/hci_core.c:937\n process_one_work kernel/workqueue.c:3322 [inline]\n process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405\n worker_thread+0x92d/0xe10 kernel/workqueue.c:3486\n kthread+0x388/0x470 kernel/kthread.c:436\n ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n </TASK>\n\nFix this by moving the queue_work() call in hci_register_dev() to after\nidr_init(&hdev->adv_monitors_idr) and msft_register(hdev) so that device\nstructures and extensions are fully initialized before asynchronous tasks\ncan access them. Additionally, assign hdev->msft_data in msft_register()\nonly after mutex_init(&msft->filter_lock) has completed.","Type":"Description","Title":"Bluetooth: hci_core: Fix race condition during device registrati"}]}}}