Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
2 versions affected across 1 product
| Date | Total | Labels |
|---|
| 2026-03-25 | 3 | General2Patch1 |
| 2026-03-26 | 1 | Disclosure1 |
| 2026-03-27 | 1 | General1 |
CVE-2026-23395 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ Currently the code attempts to acc… https://www.cve.org/CVERecord?id=CVE-2026-23395
Post summary
The Linux kernel’s Bluetooth L2CAP vulnerability CVE-2026-23395 has been fixed with a patch that stops accepting multiple L2CAP_ECRED_CONN_REQ requests.
⚡ New CVE Alert: CVE-2026-23395 🚨 Risk Level: Unknown 🧩 Affects: Multiple / Unspecified Products Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-23395 #CVE-2026-23395 #CVE #CyberSecurity #InfoSec https://t.co/DBZCIQmfA9
Post summary
A brief tweet that announces CVE‑2026‑23395 with minimal information, lacking technical or operational details.
🧠 CVE-2026-23395 is the kind of bug that screams “protocol state bug” not “movie-worthy hack.” Still: one duplicate identifier and Bluetooth flow control faceplants. https://windowsforum.com/threads/cve-2026-23395-linux-bluetooth-l2cap-ecred-fix-for-duplicate-identifier-requests.407437/ #KernelSecurity #Cve202623395 #LinuxBluetooth #L2CapEnhancedCreditBasedFlowControl https://t.co/eFrpwgRUmD
Post summary
CVE-2026-23395 is a protocol state bug involving duplicate identifiers in Linux Bluetooth L2CAP, discussed in a forum thread that references a fix, with no evidence of active exploitation or public PoC.
🚨 CYBERDUDEBIVASH SENTINEL APEX ALERT 🚨 Threat: CVE-2026-23395 - Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ Intel Report: https://ift.tt/QXnl9m3
Post summary
The post alerts about CVE‑2026‑23395 but provides only a brief technical label and a link to further intel, with no exploit, patch, or active‑use details.
CVE-2026-23395 Bluetooth L2CAP Kernel Vulnerability https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-23395
Post summary
The brief announcement merely references CVE‑2026‑23395 with minimal detail and a link, lacking concrete technical or exploit information.
9 of 9 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| OS | linux | linux_kernel | - | - | - |
| OS | linux | linux_kernel | 5.7 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |
| OS | linux | linux_kernel | 7.0 | - | - |