{"api_version":"1","generated_at":"2026-11-20T07:30:04+00:00","cve":"CVE-2026-99793","urls":{"html":"https://cve.report/CVE-2026-99793","api":"https://cve.report/api/cve/CVE-2026-99793.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99793","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99793"},"summary":{"title":"Bluetooth: L2CAP: Only accept connection responses to outstanding requests","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:18","updated_at":"2026-11-20 06:18:18"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9","name":"https://git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe","name":"https://git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf","name":"https://git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb","name":"https://git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99793","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99793","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 08ad7b94a31820eb3082851b924f76503fe66ebf git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 c6789ceaf6e28e97d73434e12c7ae60432f86dbb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 bef1f610bc1f99b349368cb8d9025c2ff66d1fbe git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.118 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/bluetooth/l2cap_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"08ad7b94a31820eb3082851b924f76503fe66ebf","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"c6789ceaf6e28e97d73434e12c7ae60432f86dbb","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"bef1f610bc1f99b349368cb8d9025c2ff66d1fbe","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/bluetooth/l2cap_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.12"},{"lessThan":"2.6.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.118","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.118","versionStartIncluding":"2.6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"2.6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"2.6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc1","versionStartIncluding":"2.6.12","vulnerable":true}],"negate":false,"operator":"OR"}]}],"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."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:53.035Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"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"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99793","datePublished":"2026-11-20T05:51:53.035Z","dateReserved":"2026-09-25T10:25:14.434Z","dateUpdated":"2026-11-20T05:51:53.035Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:18","lastModifiedDate":"2026-11-20 06:18:18","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99793","Ordinal":"1","Title":"Bluetooth: L2CAP: Only accept connection responses to outstandin","CVE":"CVE-2026-99793","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99793","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Bluetooth: L2CAP: Only accept connection responses to outstandin"}]}}}