CVE-2026-63974

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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: Set HCI_CMD_DRAIN_WORKQUEUE during device close

Since hci_dev_close_sync() can now be called during the reset path, we should also set HCI_CMD_DRAIN_WORKQUEUE. This avoids queuing timeouts while the hdev workqueue is being drained.

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
24%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60bceb9a4c693e68cc90ba4b2dfb9e000e8638ff
generic

Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/525daaea459fc215f432de1b8debbd9144bf97b0
generic

Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47330cc875b36a1cf7b3543cb2cf90a7c603ce0e

Vendor Advisories for CVE-2026-63974(2)

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

Patch Availability(6)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 17× in last 7d / 115× 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 231 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63974?
CVE-2026-63974 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: Set HCICMDDRAINWORKQUEUE during device close Since hcidevclose_sync() can now be called during the reset path, we should also set HCICMDDRAIN_WORKQUEUE. This avoids queuing timeouts while the hdev workqueue is…
When was CVE-2026-63974 disclosed?
CVE-2026-63974 was first published in the National Vulnerability Database on July 19, 2026, 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-2026-63974 actively exploited?
CVE-2026-63974 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 75.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63974?
CVE-2026-63974 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63974?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63974, 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-2026-63974

Explore →

Is Your Infrastructure Affected by CVE-2026-63974?

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