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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 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)
EPSS
16.2%
KEV
Not listed

Published

March 25, 2026

Last Modified

April 24, 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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Data Freshness Timeline

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

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

Explore the affected products and dependency analysis for 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