CVE-2026-98109

MEDIUMNVD 4.74.7—
EchelonGraph scoreHIGH confidence

Score 4.7 from GitHub Security Advisory published 2026-09-25. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_core: Fix race condition during device registration

In hci_register_dev(), the power_on work item is queued to hdev->req_workqueue before initializing hdev->adv_monitors_idr and registering the MSFT extension via msft_register(). For devices marked with quirks such as HCI_QUIRK_RAW_DEVICE, the HCI_UNCONFIGURED flag is set on the device. When the power_on work item runs concurrently on another CPU, hci_power_on() detects that the device is unconfigured and immediately invokes hci_dev_do_close(), which calls msft_do_close().

Concurrently, msft_register() allocates the msft structure and exposes it to hdev->msft_data prior to calling mutex_init(&msft->filter_lock). If msft_do_close() executes while hdev->msft_data is already assigned but the mutex has not yet been initialized, mutex_lock(&msft->filter_lock) operates on an uninitialized mutex, triggering a DEBUG_LOCKS warning:

DEBUG_LOCKS_WARN_ON(lock->magic != lock) WARNING: kernel/locking/mutex.c:625 at __mutex_lock_common kernel/locking/mutex.c:625 [inline] WARNING: kernel/locking/mutex.c:625 at __mutex_lock+0x12d8/0x1550 kernel/locking/mutex.c:821 ... Call Trace: msft_do_close+0x308/0x7b0 net/bluetooth/msft.c:693 hci_dev_close_sync+0x86b/0x10a0 net/bluetooth/hci_sync.c:5522 hci_dev_do_close net/bluetooth/hci_core.c:499 [inline] hci_power_on+0x32c/0x750 net/bluetooth/hci_core.c:937 process_one_work kernel/workqueue.c:3322 [inline] process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405 worker_thread+0x92d/0xe10 kernel/workqueue.c:3486 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

Fix this by moving the queue_work() call in hci_register_dev() to after idr_init(&hdev->adv_monitors_idr) and msft_register(hdev) so that device structures and extensions are fully initialized before asynchronous tasks can access them. Additionally, assign hdev->msft_data in msft_register() only after mutex_init(&msft->filter_lock) has completed.

CVSS v3
4.7
EG Score
4.7MEDIUMhigh confidence
EG Risk
26
EG Risk 26/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

Auto-updated Oct 2, 2026
No patch confirmed yet.
generic

Bluetooth: hci_core: Fix race condition during device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d427b1c71d9798083e954d3c13469dc0a2305868
generic

Bluetooth: hci_core: Fix race condition during device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1faf348c29e6f8302ec7769cbf1c1ef05be014f
generic

Bluetooth: hci_core: Fix race condition during device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a11ebe8dc0333fb870bbbb656b34690e87ee3f98
generic

Bluetooth: hci_core: Fix race condition during device registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18

Vendor Advisories for CVE-2026-98109(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 07:37 UTCEG score recompute
  2. 2026-10-05 07:37 UTCVendor advisory
  3. 2026-10-05 07:37 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 09:32 UTCEG score recompute
  6. 2026-10-04 09:32 UTCVendor advisory
  7. 2026-10-04 09:32 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 11:27 UTCVendor advisory
  10. 2026-10-03 11:27 UTCGHSA enrichment
  11. 2026-10-03 11:11 UTCEG score recompute
  12. 2026-10-03 11:11 UTCVendor advisory
  13. 2026-10-03 11:11 UTCGHSA enrichment
  14. 2026-10-02 17:57 UTCEPSS rescore
  15. 2026-10-02 15:23 UTCEG score recompute▲ 4.70
  16. 2026-10-02 15:23 UTCVendor advisory
  17. 2026-10-02 15:23 UTCGHSA enrichment
  18. 2026-10-02 15:22 UTCNVD updateCVSS v3 → 4.7 · severity → MEDIUM
  19. 2026-10-01 19:51 UTCEPSS rescore
  20. 2026-09-30 15:04 UTCEPSS rescore
  21. 2026-09-30 14:34 UTCEG score recompute
  22. 2026-09-30 14:34 UTCVendor advisory
  23. 2026-09-30 14:34 UTCGHSA enrichment
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 8 more
  1. 2026-09-28 12:56 UTCEG score recompute
  2. 2026-09-28 12:56 UTCVendor advisory
  3. 2026-09-28 12:56 UTCGHSA enrichment
  4. 2026-09-27 13:49 UTCEPSS rescore
  5. 2026-09-26 15:59 UTCEPSS rescore
  6. 2026-09-25 11:30 UTCNVD update
  7. 2026-09-25 10:48 UTCEG score recompute
  8. 2026-09-25 10:46 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-98109?
CVE-2026-98109 is a medium vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Fix race condition during device registration In hciregisterdev(), the power_on work item is queued to hdev->reqworkqueue before initializing hdev->advmonitors_idr and registering the MSFT extension via…
When was CVE-2026-98109 disclosed?
CVE-2026-98109 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98109 actively exploited?
CVE-2026-98109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98109?
CVE-2026-98109 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-98109?
No fix for CVE-2026-98109 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-98109 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98109

Explore →

Is Your Infrastructure Affected by CVE-2026-98109?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs