Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.253, 5.15.203, 6.1.167, 6.12.78, 6.18.20, 6.19.10, 6.6.130
- CVEs
- CVE-2026-23395
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 03:05 UTC · Revision 1
Source evidence
Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ
core-osv · Original sourcePublished 25 Mar 2026, 10:33 UTC
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.
osv:CVE-2026-23395
Kernel
Fixed versions: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10
Complete source record
{
"id": "0c5517dae245279d07451b33c844f1a4976787cb89f8506cca918e4445cad758",
"url": "https://osv.dev/vulnerability/CVE-2026-23395",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ",
"summary": "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.",
"evidence": "osv:CVE-2026-23395",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.253",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.203",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.167",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.130",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.78",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.20",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-23395",
"aliases": [
"CVE-2026-23395"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "15f02b91056253e8cdc592888f431da0731337b8"
},
{
"fixed": "10a7a702542240d5edb2b39450ac951c59ccd009"
},
{
"fixed": "46e5b71666fb7652082e4e214a3365f4b14f1dc3"
},
{
"fixed": "fb4a3a26483f3ea2cd21c7a2f7c45d5670600465"
},
{
"fixed": "2124d82fd25e1671bb3ceb37998af5aae5903e06"
},
{
"fixed": "6b949a6b33cbdf621d9fc6f0c48ac00915dbf514"
},
{
"fixed": "8d0d94f8ba5b3a0beec3b0da558b9bea48018117"
},
{
"fixed": "e72ee455297b794b852e5cea8d2d7bb17312172a"
},
{
"fixed": "5b3e2052334f2ff6d5200e952f4aa66994d09899"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23395.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.7.0"
},
{
"fixed": "5.10.253"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.203"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.167"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.130"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.78"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.20"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23395.json"
}
}
],
"modified": "2026-10-28T02:30:25.383897869Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-784472.html",
"https://git.kernel.org/stable/c/10a7a702542240d5edb2b39450ac951c59ccd009",
"https://git.kernel.org/stable/c/2124d82fd25e1671bb3ceb37998af5aae5903e06",
"https://git.kernel.org/stable/c/46e5b71666fb7652082e4e214a3365f4b14f1dc3",
"https://git.kernel.org/stable/c/5b3e2052334f2ff6d5200e952f4aa66994d09899",
"https://git.kernel.org/stable/c/6b949a6b33cbdf621d9fc6f0c48ac00915dbf514",
"https://git.kernel.org/stable/c/8d0d94f8ba5b3a0beec3b0da558b9bea48018117",
"https://git.kernel.org/stable/c/e72ee455297b794b852e5cea8d2d7bb17312172a",
"https://git.kernel.org/stable/c/fb4a3a26483f3ea2cd21c7a2f7c45d5670600465",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23395.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-23395",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23395.json"
}
},
"related_cves": [
{
"value": "CVE-2026-23395",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 492117,
"published_at": "2026-03-25T10:33:18.936+00:00"
}