CVE-2026-23395

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-25. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ

Currently the code attempts to accept requests regardless of the command identifier which may cause multiple requests to be marked as pending (FLAG_DEFER_SETUP) which can cause more than L2CAP_ECRED_MAX_CID(5) to be allocated in l2cap_ecred_rsp_defer causing an overflow.

The spec is quite clear that the same identifier shall not be used on subsequent requests:

'Within each signaling channel a different Identifier shall be used for each successive request or indication.' https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-62/out/en/host/logical-link-control-and-adaptation-protocol-specification.html#UUID-32a25a06-4aa4-c6c7-77c5-dcfe3682355d

So this attempts to check if there are any channels pending with the same identifier and rejects if any are found.

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

Published

March 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d0d94f8ba5b3a0beec3b0da558b9bea48018117
generic

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b949a6b33cbdf621d9fc6f0c48ac00915dbf514
generic

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b3e2052334f2ff6d5200e952f4aa66994d09899
generic

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2124d82fd25e1671bb3ceb37998af5aae5903e06
generic

Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10a7a702542240d5edb2b39450ac951c59ccd009

Vendor Advisories for CVE-2026-23395(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv
linuxKernel @ 6.1.167—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (119 versions)6.19.10-1—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-23395?
CVE-2026-23395 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix accepting multiple L2CAPECREDCONN_REQ Currently the code attempts to accept requests regardless of the command identifier which may cause multiple requests to be marked as pending (FLAGDEFERSETUP) which can…
When was CVE-2026-23395 disclosed?
CVE-2026-23395 was first published in the National Vulnerability Database on March 25, 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-23395 actively exploited?
CVE-2026-23395 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 83.8% of all scored CVEs.
What is the CVSS score of CVE-2026-23395?
CVE-2026-23395 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-23395?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23395, 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-23395

Explore →

Is Your Infrastructure Affected by CVE-2026-23395?

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

Start Free Scan →Browse All CVEs