In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan l2cap_new_connection() sets default value of channel mode to match the parent channel. l2cap_le_connect_req() left this at the default, and created L2CAP_MODE_EXT_FLOWCTL channels if listening pchan has that mode. This causes FLAG_DEFER_SETUP channels to reply to L2CAP_LE_CONN_REQ with L2CAP_ECRED_CONN_RSP, which is incorrect. It can also result to stack OOB write (of l2cap_alloc_cid determined values) in l2cap_ecred_rsp_defer(), as l2cap_le_connect_req() does not limit maximum number of deferred channels or check for duplicate ident. Fix by setting chan->mode correctly in l2cap_le_connect_req(). Also check channel mode in l2cap_ecred_rsp_defer(), and do WARN_ON_ONCE instead of OOB write to make it less brittle.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-19 09:14
- First seenCVSS 7.5NVD modified 2026-10-19 10:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 8
- https://git.kernel.org/stable/c/0e1fc7cab95ad958e55d70a5dfaaea687c9c639f
- https://git.kernel.org/stable/c/1074bcc57f741223f9fa82ce6afe5c3d783e4d10
- https://git.kernel.org/stable/c/4ef05db5b08b176a551b4a6287372045998806b0
- https://git.kernel.org/stable/c/564ae0e05e598aa895b9dbd18cb7d6eb64752869
- https://git.kernel.org/stable/c/5d5a625cbc854d4c4f68e4b16fcf6e682d9a9ed1
- https://git.kernel.org/stable/c/6cb79e6499228cfdbd4b3301371ce74d01cd2f80
- https://git.kernel.org/stable/c/aab17938998b29e75c3324763411aef3e300fc67
- https://git.kernel.org/stable/c/ad0f44a3f1f688558ed876a0702bc2c82b0df689