CVE-2026-23395
Linux Kernel 5.7.1 – 5.10.253
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-23395 is a high-severity Improper Input Validation (CWE-20) vulnerability in Linux Kernel. Its CVSS base score is 8.8 (High).
Operationally, ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-23395 is a vulnerability in the Linux kernel's Bluetooth L2CAP implementation that allows acceptance of multiple L2CAP_ECRED_CONN_REQ packets regardless of their command identifier. This flaw causes multiple requests to be marked as pending (FLAG_DEFER_SETUP), resulting in more than L2CAP_ECRED_MAX_CID (5) channel identifiers being allocated in l2cap_ecred_rsp_defer, leading to an overflow. The issue violates Bluetooth specifications, which require unique identifiers for each successive request on a signaling channel.
An attacker within adjacent network range (Bluetooth proximity) with no privileges or user interaction required can exploit this by sending crafted L2CAP_ECRED_CONN_REQ packets using the same identifier repeatedly. Successful exploitation achieves high impacts on confidentiality, integrity, and availability (CVSS 3.1 score of 8.8: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), potentially causing kernel resource exhaustion, denial of service, or further compromise through the overflow.
Kernel patches referenced in stable git commits (e.g., 10a7a7025422, 2124d82fd25e, 46e5b71666fb, 5b3e2052334f, 6b949a6b33cb) mitigate the issue by checking for existing pending channels with the same identifier and rejecting subsequent requests, enforcing the Bluetooth specification's uniqueness requirement. Security practitioners should update to kernels incorporating these fixes.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-15398
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.
Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.