CVE-2025-40318

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-08. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.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: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once

hci_cmd_sync_dequeue_once() does lookup and then cancel the entry under two separate lock sections. Meanwhile, hci_cmd_sync_work() can also delete the same entry, leading to double list_del() and "UAF".

Fix this by holding cmd_sync_work_lock across both lookup and cancel, so that the entry cannot be removed concurrently.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

December 8, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9cd536970192b72257afcdfba0bfc09993e6f19c
generic

Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/932c0a4f77ac13e526fdd5b42914d29c9821d389
generic

Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a94f7e017438935c09ef833a1aa908ad9875213
generic

Bluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09b0cd1297b4dbfe736aeaa0ceeab2265f47f772

Patch Availability(20)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.158-1~deb11u1 (13 versions)6.1.159-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (45 versions)6.1.159-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)6.12.63-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (76 versions)6.17.8-1

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 3× in last 7d / 24× 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.

Showing the most recent 100 of 166 total refreshes for this CVE.

  1. 2026-09-06 13:46 UTCEPSS rescore
  2. 2026-09-04 05:05 UTCEPSS rescore
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:38 UTCEPSS rescore
  6. 2026-08-30 19:16 UTCEPSS rescore
  7. 2026-08-30 01:21 UTCEPSS rescore
  8. 2026-08-28 21:40 UTCEPSS rescore
  9. 2026-08-27 14:24 UTCEPSS rescore
  10. 2026-08-26 14:45 UTCEPSS rescore
  11. 2026-08-25 13:48 UTCEPSS rescore
  12. 2026-08-24 12:30 UTCOSV refresh
  13. 2026-08-23 00:18 UTCEPSS rescore
  14. 2026-08-21 23:48 UTCEPSS rescore
  15. 2026-08-20 22:54 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:47 UTCEPSS rescore
  19. 2026-08-17 13:46 UTCEPSS rescore
  20. 2026-08-16 14:55 UTCEPSS rescore
  21. 2026-08-16 02:13 UTCEPSS rescore
  22. 2026-08-15 01:29 UTCEPSS rescore
  23. 2026-08-13 21:59 UTCEPSS rescore
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-08 16:36 UTCEPSS rescore
  2. 2026-08-08 08:20 UTCEG score recompute
  3. 2026-08-08 08:20 UTCVendor advisory
  4. 2026-08-08 08:20 UTCGHSA enrichment
  5. 2026-08-07 16:26 UTCEPSS rescore
  6. 2026-08-06 13:46 UTCEPSS rescore
  7. 2026-08-05 12:50 UTCEG score recompute
  8. 2026-08-05 12:50 UTCVendor advisory
  9. 2026-08-05 12:50 UTCGHSA enrichment
  10. 2026-08-04 15:09 UTCEPSS rescore
  11. 2026-08-04 10:37 UTCEPSS rescore
  12. 2026-08-02 02:26 UTCEPSS rescore
  13. 2026-08-01 04:15 UTCEPSS rescore
  14. 2026-07-30 16:27 UTCEPSS rescore
  15. 2026-07-30 06:24 UTCEG score recompute 8.80
  16. 2026-07-30 06:24 UTCVendor advisory
  17. 2026-07-30 06:24 UTCGHSA enrichment
  18. 2026-07-30 06:18 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  19. 2026-07-30 01:29 UTCEPSS rescore
  20. 2026-07-28 15:35 UTCEPSS rescore
  21. 2026-07-27 06:09 UTCOSV refresh
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
  26. 2026-07-23 02:55 UTCEG score recompute
  27. 2026-07-22 14:07 UTCEPSS rescore
  28. 2026-07-22 14:07 UTCEPSS rescore
  29. 2026-07-21 15:24 UTCEPSS rescore
  30. 2026-07-20 17:07 UTCEPSS rescore
  31. 2026-07-19 14:30 UTCEPSS rescore
  32. 2026-07-19 14:30 UTCEPSS rescore
  33. 2026-07-19 02:28 UTCEPSS rescore
  34. 2026-07-19 02:28 UTCEPSS rescore
  35. 2026-07-18 10:04 UTCEPSS rescore
  36. 2026-07-18 10:04 UTCEPSS rescore
  37. 2026-07-16 17:02 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 01:59 UTCEPSS rescore
  41. 2026-07-15 01:59 UTCEPSS rescore
  42. 2026-07-13 22:29 UTCEPSS rescore
  43. 2026-07-13 22:29 UTCEPSS rescore
  44. 2026-07-13 06:12 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-10 00:45 UTCOSV refresh
  49. 2026-07-09 19:09 UTCEPSS rescore
  50. 2026-07-09 19:09 UTCEPSS rescore
  51. 2026-07-07 13:45 UTCEPSS rescore
  52. 2026-07-06 16:27 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 02:23 UTCEPSS rescore
  55. 2026-07-05 02:30 UTCEPSS rescore
  56. 2026-07-04 06:30 UTCEPSS rescore
  57. 2026-07-01 15:06 UTCEPSS rescore
  58. 2026-07-01 15:06 UTCEPSS rescore
  59. 2026-06-28 14:07 UTCEPSS rescore
  60. 2026-06-28 14:07 UTCEPSS rescore
  61. 2026-06-28 04:55 UTCEPSS rescore
  62. 2026-06-28 04:55 UTCEPSS rescore
  63. 2026-06-27 03:08 UTCEPSS rescore
  64. 2026-06-27 03:08 UTCEPSS rescore
  65. 2026-06-25 13:49 UTCEPSS rescore
  66. 2026-06-25 13:49 UTCEPSS rescore
  67. 2026-06-24 14:04 UTCEPSS rescore
  68. 2026-06-24 14:04 UTCEPSS rescore
  69. 2026-06-23 21:32 UTCEPSS rescore
  70. 2026-06-23 21:32 UTCEPSS rescore
  71. 2026-06-22 14:25 UTCEPSS rescore
  72. 2026-06-22 14:25 UTCEPSS rescore
  73. 2026-06-21 14:56 UTCEPSS rescore
  74. 2026-06-21 14:56 UTCEPSS rescore
  75. 2026-06-21 11:31 UTCOSV refresh

Frequently asked(5)

What is CVE-2025-40318?
CVE-2025-40318 is a high vulnerability published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: fix race in hcicmdsyncdequeue_once hcicmdsyncdequeueonce() does lookup and then cancel the entry under two separate lock sections. Meanwhile, hcicmdsync_work() can also delete the same entry, leading to double…
When was CVE-2025-40318 disclosed?
CVE-2025-40318 was first published in the National Vulnerability Database on December 8, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40318 actively exploited?
CVE-2025-40318 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 81.0% of all scored CVEs.
What is the CVSS score of CVE-2025-40318?
CVE-2025-40318 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40318, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-40318

Explore →

Is Your Infrastructure Affected by CVE-2025-40318?

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