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-64408Bluetooth: bnep: pin L2CAP connection during netdev registration

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: pin L2CAP connection during netdev registration bnep_add_connection() reads the L2CAP connection without holding the channel lock, then passes its HCI device to register_netdev(). Controller teardown can clear and release that connection concurrently, leaving the network device registration path to dereference a freed parent device. Take a reference to the L2CAP connection while holding the channel lock. Retain it until register_netdev() has taken the parent device reference.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 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-64408, 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.26% · top 82% of all CVEs (15 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 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < 390b5db3ff8745187f094c4e915663b7b1f98944
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < 46a88784c4c9b96954dd86f747ce93f65efa1302
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < 551ae773ec64045b4e72099132654887e0270bcc
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < ae215c5b6422d8eda443b861b124bd1be6969c31
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < df22adc7eafc22e651561813c11dc51a796b12ee
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < a6b22dbd80926556290ad2243be25218d6956a19
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < 563a8573047182f550b1e1e030615755cd8c41da
    • affected 65f53e9802dbfae0e5758a91793c3f5f8bece49b – < bb067a99a0356196c0b89a95721985485ebce5a5
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .