Public vulnerability disclosure

CVE-2026-99793

Bluetooth: L2CAP: Only accept connection responses to outstanding requests

published

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Only accept connection responses to outstanding requests An outgoing channel waits in BT_CONNECT until security and the feature mask exchange complete, and only then sends its connection request. A peer can answer it before that with a connection response matching our source CID. The channel then moves to BT_CONFIG, completes configuration and becomes connected before security has completed. If security then fails, l2cap_security_cfm() leaves the connected channel alone, so it stays up on a link that did not reach the required security level. A connection response with a zero source CID is matched by identifier. Another channel can hold the same identifier for a response it still has to send, so the lookup can pick the wrong channel. Only accept a connection response while our request is outstanding, and only look at such channels when matching by identifier.

Technical severity8.1 highCVSS 3.1 · CNA: Linux
Published2026-11-20Source updated 2026-11-22
Collected2026-11-223 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < 08ad7b94a31820eb3082851b924f76503fe66ebf (affected, git)
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < c6789ceaf6e28e97d73434e12c7ae60432f86dbb (affected, git)
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < bef1f610bc1f99b349368cb8d9025c2ff66d1fbe (affected, git)
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
2.6.12 (affected)
≥ 0; < 2.6.12 (unaffected, semver)
≥ 6.12.118; ≤ 6.12.* (unaffected, semver)
≥ 6.18.64; ≤ 6.18.* (unaffected, semver)
≥ 7.3.5; ≤ 7.3.* (unaffected, semver)
≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 8.1
high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NCNA: Linux
3.1 / 8.1
high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NNVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide