CVE-2026-64408

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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

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: bnep: pin L2CAP connection during netdev registration

bnep_add_connection() reads the L2CAP connection without holding the channel lock, then passes its HCI device to register_netdev(). Controller teardown can clear and release that connection concurrently, leaving the network device registration path to dereference a freed parent device.

Take a reference to the L2CAP connection while holding the channel lock. Retain it until register_netdev() has taken the parent device reference.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/563a8573047182f550b1e1e030615755cd8c41da
generic

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/551ae773ec64045b4e72099132654887e0270bcc
generic

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46a88784c4c9b96954dd86f747ce93f65efa1302
generic

Bluetooth: bnep: pin L2CAP connection during netdev registration - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/390b5db3ff8745187f094c4e915663b7b1f98944

Vendor Advisories for CVE-2026-64408(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 32× in last 7d / 157× 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 188 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64408?
CVE-2026-64408 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: pin L2CAP connection during netdev registration bnepaddconnection() reads the L2CAP connection without holding the channel lock, then passes its HCI device to register_netdev(). Controller teardown can clear and…
When was CVE-2026-64408 disclosed?
CVE-2026-64408 was first published in the National Vulnerability Database on July 25, 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-64408 actively exploited?
CVE-2026-64408 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 82.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64408?
CVE-2026-64408 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64408?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64408, 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-64408

Explore →

Is Your Infrastructure Affected by CVE-2026-64408?

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

Start Free Scan →Browse All CVEs