CVE-2026-23395: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ
Bluetooth: L2CAP: Fix accepting multiple L2CAPECREDCONNREQ
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.130.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Compensating control
For Bluetooth L2CAP, check for channels already pending with the same command identifier and reject subsequent L2CAP_ECRED_CONN_REQ requests using that identifier.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23395?
CVE-2026-23395 has a moderate severity level due to the potential for exploitation via multiple L2CAP_ECRED_CONN_REQ connections.
How do I fix CVE-2026-23395?
To fix CVE-2026-23395, update the Linux kernel to the latest version that includes the security patch addressing the L2CAP vulnerability.
What are the potential impacts of CVE-2026-23395 if exploited?
If exploited, CVE-2026-23395 could lead to denial-of-service conditions or allow an attacker to disrupt Bluetooth communication.
Which versions of the Linux kernel are affected by CVE-2026-23395?
CVE-2026-23395 affects various versions of the Linux kernel that implement Bluetooth L2CAP functionalities prior to the patch release.
Is CVE-2026-23395 related to Bluetooth functionalities in Linux?
Yes, CVE-2026-23395 specifically addresses a vulnerability in the Bluetooth L2CAP layer of the Linux kernel.