# CVE-2026-99793: Bluetooth: L2CAP: Only accept connection responses to outstanding requests

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < 08ad7b94a31820eb3082851b924f76503fe66ebf (affected, git); ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < c6789ceaf6e28e97d73434e12c7ae60432f86dbb (affected, git); ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < bef1f610bc1f99b349368cb8d9025c2ff66d1fbe (affected, git); ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2; < a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 (affected, git). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 8.1 (high); CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N; source: CNA: Linux

- CVSS 3.1: 8.1 (high); CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.58%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

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

## References

- https://git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf (CNA: Linux)

- https://git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb (CNA: Linux)

- https://git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe (CNA: Linux)

- https://git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 (CNA: Linux)

- https://git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99793; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99793; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99793; retrieved 2026-11-22; source updated Not reported

Revision: cdd748469dc1e454a8d99095c269d7555d7985b85fb47e81a60ba25fecb683b9

Canonical: https://y2.dev/cve/CVE-2026-99793

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.