Review reviewHigh

CVE-2026-53071

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8

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_con...

CVSS
8.8
EPSS
0.26%
17.7% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.26%
Technical severityCVSS 8.8

Vulnerability overview

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_con...

Affected product and versions

Product
Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8
Affected versions
>= 15f02b91056253e8cdc592888f431da0731337b8 < 96dca51715d86559ed6ed8028e5445cecb80f3ae, >= 15f02b91056253e8cdc592888f431da0731337b8 < 330b20ec97916961ee0e6c29c06bc0fa7c96e64c, >= 15f02b91056253e8cdc592888f431da0731337b8 < 0ccd75c51f620374086f359e906917676e699a1c, >= 15f02b91056253e8cdc592888f431da0731337b8 < 77a853aec710b2fdf41fa298ea3cbc9a4358f917, >= 15f02b91056253e8cdc592888f431da0731337b8 < fe1188abdae9b7a8199dcdfcf9244d5e5d61eb14, >= 15f02b91056253e8cdc592888f431da0731337b8 < dc89961b76f12aff47124c1df4bdb32a080f4d0c, >= 15f02b91056253e8cdc592888f431da0731337b8 < 5501d055a1ce3c747141e3955ba8cf034d193f3e, >= 15f02b91056253e8cdc592888f431da0731337b8 < 42776497cdbc9a665b384a6dcb85f0d4bd927eab, >= 5.7, >= 5.7 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-414, CWE-416, CWE-667