CVE-2026-99793
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/08ad7b94a31820eb3082851b924f76503fe66ebf
- git.kernel.org/stable/c/a518b9a9ef6ee3b18ecdf6ba5360c608aaf969e9
- git.kernel.org/stable/c/bef1f610bc1f99b349368cb8d9025c2ff66d1fbe
- git.kernel.org/stable/c/c6789ceaf6e28e97d73434e12c7ae60432f86dbb
- nvd.nist.gov/vuln/detail/CVE-2026-99793
- cve.org/CVERecord?id=CVE-2026-99793
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.