CVE-2026-68394

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

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

Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update

MGMT_OP_LOAD_CONN_PARAM queues conn_update_sync() when a single parameter update changes an existing LE central connection. The queued work currently stores a borrowed hci_conn_params entry from hdev->le_conn_params. A later LOAD_CONN_PARAM request can clear disabled parameters and free that entry before hci_cmd_sync_work() runs the queued callback.

Do not keep the borrowed hci_conn_params pointer in queued work. Queue the hci_conn instead and hold a reference until the queued callback completes. When the work runs, revalidate that the connection is still present, look up the current hci_conn_params entry, and cancel the update if userspace removed that entry while the work was pending.

Copy the interval values from the current params entry under hdev->lock, then drop the lock and keep using hci_le_conn_update_sync() to issue the update.

Validation reproduced this kernel report: BUG: KASAN: slab-use-after-free in conn_update_sync+0x2a/0xf0 [bluetooth] Read of size 1 at addr ffff88810c697126 by task kworker/u17:0/377 Workqueue: hci0 hci_cmd_sync_work [bluetooth]

Call Trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x5f0 kasan_report+0xe0/0x110 conn_update_sync+0x2a/0xf0 [bluetooth] hci_cmd_sync_work+0x187/0x210 [bluetooth] process_one_work+0x4fd/0xbc0 worker_thread+0x2d8/0x570 kthread+0x1ad/0x1f0 ret_from_fork+0x3c9/0x540 ret_from_fork_asm+0x1a/0x30

Allocated by task 466: hci_conn_params_add+0xa6/0x240 [bluetooth] load_conn_param+0x4e1/0x850 [bluetooth] hci_sock_sendmsg+0x96b/0xf80 [bluetooth]

Freed by task 474: kfree+0x313/0x590 hci_conn_params_clear_disabled+0x9b/0xc0 [bluetooth] load_conn_param+0x4bf/0x850 [bluetooth] hci_sock_sendmsg+0x96b/0xf80 [bluetooth]

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65ce6fe1b92112ba9064ded932c03180da3dd230
generic

Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57059ff14d81df4a970b2ea8d8f54431bb91a025
generic

Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2bf282f8f715f5d05d6f4c49ffb3bd241c5e667e

Vendor Advisories for CVE-2026-68394(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 40× 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-08-21 03:27 UTCEG score recompute
  2. 2026-08-21 03:27 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:17 UTCGHSA enrichment
  5. 2026-08-20 00:35 UTCEG score recompute
  6. 2026-08-20 00:35 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 11:24 UTCGHSA enrichment
  9. 2026-08-18 22:14 UTCGHSA enrichment
  10. 2026-08-18 08:57 UTCGHSA enrichment
  11. 2026-08-17 19:46 UTCEG score recompute
  12. 2026-08-17 19:46 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:31 UTCEG score recompute
  15. 2026-08-17 06:31 UTCGHSA enrichment
  16. 2026-08-17 05:36 UTCEG score recompute
  17. 2026-08-17 05:36 UTCGHSA enrichment
  18. 2026-08-16 17:39 UTCEG score recompute
  19. 2026-08-16 17:39 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:25 UTCEG score recompute
  22. 2026-08-16 04:25 UTCGHSA enrichment
  23. 2026-08-15 15:15 UTCGHSA enrichment
  24. 2026-08-15 02:04 UTCEG score recompute
  25. 2026-08-15 02:04 UTCGHSA enrichment
Show 15 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 12:54 UTCEG score recompute
  3. 2026-08-14 12:54 UTCGHSA enrichment
  4. 2026-08-13 23:44 UTCEG score recompute
  5. 2026-08-13 23:44 UTCGHSA enrichment
  6. 2026-08-13 23:03 UTCEG score recompute▲ 7.80
  7. 2026-08-13 23:03 UTCGHSA enrichment
  8. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 13:01 UTCEG score recompute
  11. 2026-08-13 13:01 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-10 13:24 UTCNVD update
  14. 2026-08-10 12:18 UTCEG score recompute
  15. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68394?
CVE-2026-68394 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: revalidate LOADCONNPARAM queued update MGMTOPLOADCONNPARAM queues connupdatesync() when a single parameter update changes an existing LE central connection. The queued work currently stores a borrowed hciconnparams…
When was CVE-2026-68394 disclosed?
CVE-2026-68394 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68394 actively exploited?
CVE-2026-68394 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68394?
CVE-2026-68394 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68394?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68394, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68394

Explore →

Is Your Infrastructure Affected by CVE-2026-68394?

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

Start Free Scan →Browse All CVEs