{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99793","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.434Z","datePublished":"2026-11-20T05:51:53.035Z","dateUpdated":"2026-11-22T11:10:09.380Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:10:09.380Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Only accept connection responses to outstanding requests\n\nAn outgoing channel waits in BT_CONNECT until security\nand the feature mask exchange complete, and only then\nsends its connection request. A peer can answer it\nbefore that with a connection response matching our\nsource CID. The channel then moves to BT_CONFIG,\ncompletes configuration and becomes connected before\nsecurity has completed. If security then fails,\nl2cap_security_cfm() leaves the connected channel\nalone, so it stays up on a link that did not reach\nthe required security level.\n\nA connection response with a zero source CID is\nmatched by identifier. Another channel can hold the\nsame identifier for a response it still has to send,\nso the lookup can pick the wrong channel.\n\nOnly accept a connection response while our request\nis outstanding, and only look at such channels when\nmatching by identifier."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":8.1,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:A - A remote BR/EDR peer puts L2CAP_CONN_RSP (code 0x03) on signaling CID 0x0001. hci_acldata_packet() passes that ACL frame to l2cap_recv_acldata(), l2cap_sig_channel(), l2cap_bredr_sig_cmd(), and l2cap_connect_create_rsp(). Classic Bluetooth is not routable IP, so the vector is adjacent.\nAC:L - The peer withholds L2CAP_INFO_RSP, so l2cap_do_start() leaves the outgoing channel in BT_CONNECT with CONF_CONNECT_PEND clear, then sends L2CAP_CONN_RSP. l2cap_alloc_cid() assigns scid from 0x0040, and the peer also supplies the later HCI auth result. No outside race is required.\nPR:N - l2cap_bredr_sig_cmd() handles L2CAP_CONN_RSP before l2cap_chan_check_security() or hci_conn_security() succeeds, with no host uid or capability check. An unpaired adjacent device is enough.\nUI:N - While l2cap_chan_connect() has the channel in BT_CONNECT, the peer's L2CAP_CONN_RSP and configuration replies drive l2cap_chan_ready() before pairing completes. l2cap_security_cfm() does not involve the user if that auth later fails.\nS:U - l2cap_chan_ready() only marks that l2cap_chan BT_CONNECTED and wakes its socket. The effect stays in the host kernel Bluetooth stack and does not cross a VM, IOMMU, or sandbox boundary.\nC:H - l2cap_connect_create_rsp() accepts the response before l2cap_chan_check_security() or l2cap_check_enc_key_size(), and l2cap_config_rsp() then calls l2cap_chan_ready(). l2cap_security_cfm() leaves that BT_CONNECTED channel up on auth failure, so the peer reads what the socket sends below chan->sec_level.\nI:H - After l2cap_chan_ready(), l2cap_data_channel() delivers the peer's PDUs to chan->ops->recv. That is service traffic l2cap_do_start() would have refused until hci_conn_security() met chan->sec_level.\nA:N - l2cap_connect_create_rsp() only changes l2cap_chan state, and a failed auth in l2cap_security_cfm() skips teardown. There is no freed object, overrun, or fault; a non-success result uses the existing l2cap_chan_del() path."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["net/bluetooth/l2cap_core.c"],"versions":[{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"08ad7b94a31820eb3082851b924f76503fe66ebf","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"c6789ceaf6e28e97d73434e12c7ae60432f86dbb","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"bef1f610bc1f99b349368cb8d9025c2ff66d1fbe","status":"affected","versionType":"git"},{"version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","lessThan":"a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["net/bluetooth/l2cap_core.c"],"versions":[{"version":"2.6.12","status":"affected"},{"version":"0","lessThan":"2.6.12","status":"unaffected","versionType":"semver"},{"version":"6.12.118","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.64","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.5","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.12","versionEndExcluding":"6.12.118"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.12","versionEndExcluding":"6.18.64"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.12","versionEndExcluding":"7.3.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"2.6.12","versionEndExcluding":"7.4-rc1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf"},{"url":"https://git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb"},{"url":"https://git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe"},{"url":"https://git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9"}],"title":"Bluetooth: L2CAP: Only accept connection responses to outstanding requests","x_generator":{"engine":"bippy-1.2.0"}}}}