# CVE-2026-53071: Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp

> A remote attacker can trigger a race condition in the Linux kernel Bluetooth stack to corrupt memory, potentially leading to code execution or system crash.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-53071, DEBIAN-CVE-2026-53071, GHSA-g7cw-xhg8-933g, ROOT-OS-DEBIAN-11-CVE-2026-53071, ROOT-OS-DEBIAN-12-CVE-2026-53071, ROOT-OS-UBUNTU-2204-CVE-2026-53071, ROOT-OS-UBUNTU-2404-CVE-2026-53071, UBUNTU-CVE-2026-53071

## What is CVE-2026-53071?

CVE-2026-53071 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp

l2cap_ecred_reconf_rsp() calls l2cap_chan_del() without holding
l2cap_chan_lock(). Every other l2cap_chan_del() caller in the file
acquires the lock first. A remote BLE device can send a crafted
L2CAP ECRED reconfiguration response to corrupt the channel list
while another thread is iterating it.

Add l2cap_chan_hold() and l2cap_chan_lock() before l2cap_chan_del(),
and l2cap_chan_unlock() and l2cap_chan_put() after, matching the
pattern used in l2cap_ecred_conn_rsp() and l2cap_conn_del().

Weakness: CWE-667 (Improper Locking), CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-53071?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53071?

Apply the vendor's patch.

## Is CVE-2026-53071 being exploited?

There is no known exploitation of CVE-2026-53071 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53071 and fix it if it is affected.

What it is: CVE-2026-53071 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53071 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53071/ (Markdown: https://insights.sbomify.com/CVE-2026-53071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53071
- OSV: https://osv.dev/vulnerability/CVE-2026-53071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53071/
Summaries are generated and may contain mistakes; the official description above is the record.