CVE-2026-53276: Linux Kernel Bluetooth ISO Use-After-Free Vulnerability
A use-after-free vulnerability exists in the Linux kernel's Bluetooth ISO implementation. When a socket is being rebound, the code releases a lock while still holding a cached pointer to a connection structure. Between the unlock and the next lock acquisition, a concurrent close operation can destroy that connection and deallocate its memory. The code then attempts to use the freed pointer, causing a crash or potential code execution. The issue affects local attackers with basic privileges who can interact with Bluetooth ISO sockets on the affected system.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-416
- Affected products
- 7 configuration(s)
- Published / Modified
- 2026-06-25 / 2026-07-08
NVD description (verbatim)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Fix a use-after-free of the hci_conn pointer In iso_sock_rebind_bc(), the bis pointer is cached, then the socket lock is dropped: bis = iso_pi(sk)->conn->hcon; /* Release the socket before lookups since that requires hci_dev_lock * which shall not be acquired while holding sock_lock for proper * ordering. */ release_sock(sk); hci_dev_lock(bis->hdev); During the unlocked window, could a concurrent close() destroy the connection and free the bis structure, causing hci_dev_lock(bis->hdev) to access memory after it is freed, fix this by using the hdev reference which was safely acquired via iso_conn_get_hdev().
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53276 is a use-after-free vulnerability (CWE-416) in the Linux kernel's Bluetooth ISO layer, specifically in the iso_sock_rebind_bc() function. The vulnerability occurs when a bis (Broadcast ISO Set) pointer is cached from iso_pi(sk)->conn->hcon, the socket lock is released to perform a blocking hci_dev_lock operation, and a concurrent close() call destroys the connection structure during that unlocked window. Subsequent dereferencing of the freed bis pointer causes a use-after-free condition. The fix involves obtaining a safe reference to the hci_device via iso_conn_get_hdev() prior to releasing the socket lock, eliminating the stale pointer dereference.
Business impact
This vulnerability could allow a local, authenticated attacker to crash the Linux kernel through a malformed Bluetooth ISO socket sequence, resulting in denial of service. While a direct privilege escalation vector has not been confirmed, use-after-free bugs in kernel memory management can potentially be exploited to read or write kernel memory, depending on heap feng-shui and mitigation effectiveness. Systems relying on Bluetooth connectivity and running vulnerable kernels face operational risk.
Affected systems
The Linux kernel is affected; specific version ranges depend on when the vulnerable code was introduced and when patches are released. Distributions and embedded systems shipping the affected kernel—particularly those with Bluetooth ISO support enabled—are impacted. The vulnerability requires local access and is not remotely exploitable. Check your kernel version and distribution advisories against the official Linux kernel patch repository.
Exploitability
This is a local privilege level vulnerability (CVSS:3.1/AV:L/AC:L/PR:L) with low attack complexity. Exploitation requires a local user and basic capability to open and manipulate Bluetooth ISO sockets. The race condition window may be narrow, but deterministic exploitation is possible through deliberate concurrent socket operations. The vulnerability does not appear to be in any known exploit frameworks at this time and is not tracked in the CISA KEV catalog.
Remediation
Apply the kernel patch that replaces the unsafe bis pointer caching with a reference obtained via iso_conn_get_hdev(), which safely maintains a reference to the hci_device across the unlock/lock window. Verify the patch details against your Linux distribution's security advisory or the kernel.org patch repository. Most major distributions will release updated kernel packages; prioritize systems handling Bluetooth ISO traffic.
Patch guidance
Obtain the patched kernel version from your Linux distribution's security repositories. Kernel patches for this vulnerability address the iso_sock_rebind_bc() function to use a safe hci_device reference rather than a cached connection pointer. Verify the patch has been integrated into your target kernel version before deployment. Reboot is required to activate kernel changes. For systems unable to patch immediately, consider disabling Bluetooth ISO if the system's workload permits.
Detection guidance
Monitor kernel logs for use-after-free errors or NULL pointer dereference panics related to Bluetooth ISO or HCI device operations. Dynamic analysis tools such as KASAN (Kernel Address Sanitizer) can detect this vulnerability when enabled at build time. Runtime detection is difficult without instrumentation; focus detection efforts on patch verification and version auditing. In production, watch for unexpected kernel crashes coinciding with Bluetooth ISO socket activity.
Why prioritize this
Although not yet in CISA's KEV catalog, this high-severity (CVSS 7.8) local kernel vulnerability affecting a widely used subsystem warrants expedited patching. The low attack complexity and requirement for only basic local privileges mean any multi-user Linux system or container environment is at risk. Availability impact is immediate (denial of service); confidentiality and integrity risks are potential but serious. Prioritize patching systems with multiple local users or those running Bluetooth-intensive workloads.
Risk score, explained
The CVSS 3.1 score of 7.8 reflects a local vector (no remote exploitation), low attack complexity (standard race condition, no special tools needed), and complete compromise of availability plus potential compromise of confidentiality and integrity. The severity is elevated by the kernel-level impact and the broad presence of affected components. Organizations must assess their exposure based on local user population and Bluetooth ISO adoption.
Frequently asked questions
Can this be exploited remotely?
No. The vulnerability requires local code execution and interaction with Bluetooth ISO sockets on the target system. Remote attackers cannot trigger this directly, but compromised accounts or unprivileged local users could attempt exploitation.
Does this affect all Linux systems?
Only systems with the Bluetooth ISO subsystem enabled and running a vulnerable kernel version are affected. Embedded and IoT devices with Bluetooth support may be at higher risk. Check your kernel configuration and version against distribution advisories.
What is the difference between this patch and the original vulnerable code?
The patch replaces unsafe caching of a connection pointer (bis) across an unlock/lock window with a safe reference to the hci_device obtained via iso_conn_get_hdev(). This ensures the underlying device object remains valid even if the connection is concurrently destroyed.
If we disable Bluetooth, are we protected?
Disabling Bluetooth or the ISO subsystem in the kernel configuration eliminates the attack surface for this specific vulnerability. However, patching is the recommended long-term solution for systems that require Bluetooth functionality.
This analysis is based on publicly available vulnerability information current as of the publication date. Specific patch versions, affected kernel releases, and remediation timelines must be verified against official Linux distribution security advisories and kernel.org sources. No guarantee is made regarding patch availability or timeline. Security teams should independently verify all technical details before making remediation decisions. This explainer does not constitute security advice specific to any organization's environment. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10001HIGHChrome Sandbox Escape via PerformanceManager Use-After-Free
- CVE-2026-10002HIGHGoogle Chrome PDFium Use-After-Free Vulnerability (CVSS 8.8)
- CVE-2026-10003HIGHChrome Use-After-Free Code Execution Vulnerability Analysis
- CVE-2026-10007HIGHChrome Use-After-Free in SVG Arbitrary Code Execution (CVSS 8.8)
- CVE-2026-10012HIGHChrome Skia Use-After-Free Sandbox Escape (v148.0.7778.216)
- CVE-2026-10013HIGHUse-After-Free in Chrome WebCodecs – Patch Guide & Risk Assessment
- CVE-2026-10016HIGHUse-After-Free in Chrome DOM – Sandbox Code Execution Vulnerability
- CVE-2026-10882HIGHCritical Chrome Use-After-Free RCE Vulnerability – Exploit Details & Patch Guidance