Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53358Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53358, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < 3634cbdc2eb414b69ffa752ddbe5e0458518e321
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < e1c100e2d61bd8c718b7d91fe3e050780a9bf72d
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < 89dec92041717b027216e110599e4f6d6c921b79
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < 50dfec218808b148ab4247b1858031b7a32015c5
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < 859d3ace791ed878ae9ba5522c7844d960da8f88
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < 7555fd885a0603f50e49a655850a1f2bd8a25398
    • affected 3df91ea20e744344100b10ae69a17211fcf5b207 – < 8c8e620467a7b51562dbcefbd1f09f288d7d710d
  • Linux · Linux

    • affected 3.4
    • unaffected < 3.4
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53358 badge
[![CVE-2026-53358](https://cveledger.app/badge/CVE-2026-53358.svg)](https://cveledger.app/cve/CVE-2026-53358)

Record last updated .