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-52918Bluetooth: serialize accept_q access

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: serialize accept_q access bt_sock_poll() walks the accept queue without synchronization, while child teardown can unlink the same socket and drop its last reference. The unsynchronized accept queue walk has existed since the initial Bluetooth import. Protect accept_q with a dedicated lock for queue updates and polling. Also rework bt_accept_dequeue() to take temporary child references under the queue lock before dropping it and locking the child socket.

Timeline

  1. ID reserved

    By Linux

  2. · 15 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-52918, 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.22% · top 88% of all CVEs (18 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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d9ce4de05df2385c19e2c7d12f529144e1a44af1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 41c8c1c7923e86e0eb59cfb4279349112756a336
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4ec17782fd186f901a7329605d11048b085b945a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < be43e6b4043113c3b3cf887c3c8350f67140274c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 85f8674cae82053f1e6bab295f6a8422cca14db5
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8b4c412e001b0c670eb937beab491af974da55b3
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a218bf69eb51fefe59a3976fa8925261141f681c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e83f5e24da741fa9405aeeff00b08c5ee7c37b88
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 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-52918 badge
[![CVE-2026-52918](https://cveledger.app/badge/CVE-2026-52918.svg)](https://cveledger.app/cve/CVE-2026-52918)

Record last updated .