Bug 2577655 (CVE-2026-99793) - CVE-2026-99793 kernel: kernel: Security bypass in Bluetooth L2CAP via premature connection response
Summary: CVE-2026-99793 kernel: kernel: Security bypass in Bluetooth L2CAP via prematu...
Keywords:
Status: NEW
Alias: CVE-2026-99793
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:06 UTC by OSIDB Bzimport
Modified: 2026-11-20 10:02 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:06:35 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.