PatchSiren cyber security CVE debrief
CVE-2026-74540 Linux CVE debrief
A use-after-free vulnerability exists in the Linux kernel's Bluetooth L2CAP module. The vulnerability is triggered when the `l2cap_le_connect_rsp` function obtains a channel via `__l2cap_get_chan_by_ident` but fails to hold a reference or use `l2cap_chan_hold_unless_zero` before locking and operating on it. A concurrent `l2cap_chan_del` triggered by a remote disconnect can free the channel between the lookup and `l2cap_chan_lock`, causing a use-after-free.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-15
- Original CVE updated
- 2026-10-16
- Advisory published
- 2026-08-15
- Advisory updated
- 2026-10-16
Who should care
Linux kernel developers and maintainers, Bluetooth L2CAP module developers, and organizations using Linux-based systems with Bluetooth capabilities should assess their exposure and apply patches or mitigations as needed.
Why it matters
The CVE-2026-74540 vulnerability in the Linux kernel's Bluetooth L2CAP module requires immediate attention from developers and administrators. A use-after-free vulnerability can be triggered by a remote disconnect, potentially leading to denial of service or code execution. Linux kernel developers, maintainers, and organizations using Linux-based systems with Bluetooth capabilities should assess their exposure and apply patches or mitigations as needed.
- Potential denial of service due to use-after-free vulnerability
- Possible code execution or privilege escalation
- Need for patching or mitigation to prevent exploitation
- Verification of Linux kernel versions and Bluetooth L2CAP module configurations required
Technical summary
The `l2cap_le_connect_rsp` function in the Linux kernel's Bluetooth L2CAP module does not properly handle channel references, leading to a use-after-free vulnerability. An attacker can trigger this vulnerability by initiating a remote disconnect, potentially causing a denial of service or code execution. The vulnerability exists due to a missing reference hold or use of `l2cap_chan_hold_unless_zero` before locking and operating on the channel. A concurrent `l2cap_chan_del` triggered by a remote disconnect can free the channel between the lookup and `l2cap_chan_lock`, causing a use-after-free. Linux kernel developers, maintainers, and organizations using Linux-based systems with Bluetooth capabilities should be
Defensive priority
High
Recommended defensive actions
- Review and apply the provided patches to the Linux kernel
- Ensure that the Linux kernel is updated to a version that includes the fix
- Monitor Bluetooth L2CAP activity for potential exploitation attempts
- Verify Linux kernel versions and Bluetooth L2CAP module configurations
- Assess exposure and apply patches or mitigations as needed
- Track exceptions and retest remediated assets
- Review compensating controls for exposed systems while remediation is scheduled
Evidence notes
The CVE record and source item provide details about the vulnerability, including its description and affected versions. However, the corpus does not establish specific exploitation or impact details, requiring verification from official sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-74540 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-74540
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-74540 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74540
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/74xxx/CVE-2026-74540.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/15d6c2367217a6a20b1abae9f38ded716bf620f1
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1818180fe12d6cec7a437bc59cde8efdf6b10250
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/8325eafb38c3dee5af329266393763693d17381b
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/fd4c1e301bdec60a40728ea37de531cbccda501a
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/522b730c62c53a1981604fd73524697fd347830d
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/09f447accc2570751e7d17f0dc0788b40d3edade
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.