CVE-2026-53071

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp

HIGH
8.8
CVSS Score
Published: June 24, 2026 at 04:30 PM UTC
Updated: October 19, 2026 at 08:18 PM UTC
2 products affected across 2 vendorsLinux KernelEnterprise Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1755.7 ≤ v < 5.10.2586.13 ≤ v < 6.18.336.19 ≤ v < 7.0.106.2 ≤ v < 6.6.1416.7 ≤ v < 6.12.9115f02b91056253e8cdc592888f431da0731337b85.7
Vendor states this is fixed in 0ccd75c51f620374086f359e906917676e699a1c (fixed)
Vendor states this is fixed in 330b20ec97916961ee0e6c29c06bc0fa7c96e64c (fixed)
Vendor states this is fixed in 42776497cdbc9a665b384a6dcb85f0d4bd927eab (fixed)
Vendor states this is fixed in 5501d055a1ce3c747141e3955ba8cf034d193f3e (fixed)
Vendor states this is fixed in 77a853aec710b2fdf41fa298ea3cbc9a4358f917 (fixed)
Vendor states this is fixed in 96dca51715d86559ed6ed8028e5445cecb80f3ae (fixed)
Vendor states this is fixed in dc89961b76f12aff47124c1df4bdb32a080f4d0c (fixed)
Vendor states this is fixed in fe1188abdae9b7a8199dcdfcf9244d5e5d61eb14 (fixed)
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.91 (unaffected)
Vendor states this is fixed in 6.18.33 (unaffected)
Vendor states this is fixed in 6.6.141 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 0:4.18.0-305.206.1.el8_4 (unaffected)
Vendor states this is fixed in 0:4.18.0-372.213.1.el8_6 (unaffected)
Vendor states this is fixed in 0:4.18.0-553.146.1.el8_10 (unaffected)
Vendor states this is fixed in 0:4.18.0-553.146.1.rt7.487.el8_10 (unaffected)
Vendor states this is fixed in 0:5.14.0-687.29.1.el9_8 (unaffected)
Vendor states this is fixed in 0:6.12.0-211.37.1.el10_2 (unaffected)
Vendor states this is fixed in 6 (unaffected)
Vendor states this is fixed in 7 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-414CWE-416CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card