High [CVE-2026-53071] Add missing chan lock in l2cap_ecred_reconf_rsp
This high-severity Red Hat Linux advisory covers CVE-2026-53071 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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().
A flaw was found in the Linux kernel's Bluetooth Logical Link Control and Adaptation Protocol (L2CAP) implementation. This can lead to the corruption of the channel list, potentially causing a Denial of Service (DoS) by making the system unstable or unresponsive.
The vulnerability is due to a missing channel lock when a channel is deleted. The issue is adjacent network reachable rather than Internet reachable because Bluetooth radio proximity is required.
Red Hat severity: Moderate — CVSS 7.5 (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-416.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
- kernel-0:6.12.0-211.37.1.el10_2
- kernel-rt-0:4.18.0-553.146.1.rt7.487.el8_10
- kernel-0:4.18.0-553.146.1.el8_10
- kernel-0:4.18.0-305.206.1.el8_4
- kernel-0:4.18.0-372.213.1.el8_6
- kernel-0:5.14.0-687.29.1.el9_8
- kernel-0:5.14.0-284.191.1.el9_2
- kernel-rt-0:5.14.0-284.191.1.rt14.476.el9_2
- RHSA-2026:42919
- RHSA-2026:42550
- RHSA-2026:42552
- RHSA-2026:65710
- RHSA-2026:65711
- RHSA-2026:43307
- RHSA-2026:67723
- RHSA-2026:67721
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Mitigation
Upgrade to a fixed release: kernel-0:6.12.0-211.37.1.el10_2, kernel-rt-0:4.18.0-553.146.1.rt7.487.el8_10, kernel-0:4.18.0-553.146.1.el8_10, kernel-0:4.18.0-305.206.1.el8_4, kernel-0:4.18.0-372.213.1.el8_6, kernel-0:5.14.0-687.29.1.el9_8. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.