Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 0.3%
exploitation probability
0.3%top 82% of all CVEs
observed exploitation
nono source reports it
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().
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://access.redhat.com/errata/RHSA-2026:42550https://access.redhat.com/errata/RHSA-2026:42552https://access.redhat.com/errata/RHSA-2026:42919https://access.redhat.com/errata/RHSA-2026:43307https://access.redhat.com/security/cve/CVE-2026-53071https://bugzilla.redhat.com/show_bug.cgi?id=2492458https://git.kernel.org/stable/c/0ccd75c51f620374086f359e906917676e699a1chttps://git.kernel.org/stable/c/330b20ec97916961ee0e6c29c06bc0fa7c96e64chttps://git.kernel.org/stable/c/42776497cdbc9a665b384a6dcb85f0d4bd927eabhttps://git.kernel.org/stable/c/5501d055a1ce3c747141e3955ba8cf034d193f3ehttps://git.kernel.org/stable/c/77a853aec710b2fdf41fa298ea3cbc9a4358f917https://git.kernel.org/stable/c/96dca51715d86559ed6ed8028e5445cecb80f3ae