CVE-2026-52918

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
18.0%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e83f5e24da741fa9405aeeff00b08c5ee7c37b88
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9ce4de05df2385c19e2c7d12f529144e1a44af1
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be43e6b4043113c3b3cf887c3c8350f67140274c
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a218bf69eb51fefe59a3976fa8925261141f681c
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b4c412e001b0c670eb937beab491af974da55b3
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85f8674cae82053f1e6bab295f6a8422cca14db5
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ec17782fd186f901a7329605d11048b085b945a
generic

Bluetooth: serialize accept_q access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41c8c1c7923e86e0eb59cfb4279349112756a336

Vendor Advisories for CVE-2026-52918(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 53× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 05:55 UTCEG score recompute
  2. 2026-07-07 05:55 UTCVendor advisory
  3. 2026-07-07 05:55 UTCGHSA enrichment
  4. 2026-07-06 18:41 UTCEG score recompute
  5. 2026-07-06 18:41 UTCVendor advisory
  6. 2026-07-06 18:41 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 06:45 UTCEG score recompute
  10. 2026-07-06 06:45 UTCVendor advisory
  11. 2026-07-06 06:45 UTCGHSA enrichment
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 19:32 UTCEG score recompute
  15. 2026-07-05 19:32 UTCVendor advisory
  16. 2026-07-05 19:32 UTCGHSA enrichment
  17. 2026-07-05 08:19 UTCEG score recompute
  18. 2026-07-05 08:19 UTCVendor advisory
  19. 2026-07-05 08:19 UTCGHSA enrichment
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 21:05 UTCEG score recompute
  22. 2026-07-04 21:05 UTCVendor advisory
  23. 2026-07-04 21:05 UTCGHSA enrichment
  24. 2026-07-04 09:53 UTCEG score recompute
  25. 2026-07-04 09:53 UTCVendor advisory
Show 41 more
  1. 2026-07-04 09:52 UTCGHSA enrichment
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-03 22:37 UTCEG score recompute
  4. 2026-07-03 22:37 UTCVendor advisory
  5. 2026-07-03 22:37 UTCGHSA enrichment
  6. 2026-07-03 11:25 UTCEG score recompute
  7. 2026-07-03 11:25 UTCVendor advisory
  8. 2026-07-03 11:25 UTCGHSA enrichment
  9. 2026-07-03 00:00 UTCEG score recompute
  10. 2026-07-03 00:00 UTCVendor advisory
  11. 2026-07-03 00:00 UTCGHSA enrichment
  12. 2026-07-02 12:47 UTCEG score recompute
  13. 2026-07-02 12:47 UTCVendor advisory
  14. 2026-07-02 12:47 UTCGHSA enrichment
  15. 2026-07-02 01:35 UTCEG score recompute
  16. 2026-07-02 01:35 UTCVendor advisory
  17. 2026-07-02 01:35 UTCGHSA enrichment
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-07-01 14:22 UTCEG score recompute
  20. 2026-07-01 14:22 UTCVendor advisory
  21. 2026-07-01 14:22 UTCGHSA enrichment
  22. 2026-07-01 03:10 UTCEG score recompute
  23. 2026-07-01 03:10 UTCVendor advisory
  24. 2026-07-01 03:09 UTCGHSA enrichment
  25. 2026-06-30 23:22 UTCEPSS rescore
  26. 2026-06-30 15:56 UTCEG score recompute▲ 8.80
  27. 2026-06-30 15:56 UTCVendor advisory
  28. 2026-06-30 15:55 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-27 12:18 UTCEG score recompute
  36. 2026-06-27 12:18 UTCGHSA enrichment
  37. 2026-06-27 03:08 UTCEPSS rescore
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-24 14:05 UTCEPSS rescore
  40. 2026-06-24 08:42 UTCEG score recompute
  41. 2026-06-24 08:40 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52918?
CVE-2026-52918 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: serialize accept_q access btsockpoll() 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…
When was CVE-2026-52918 disclosed?
CVE-2026-52918 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52918 actively exploited?
CVE-2026-52918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52918?
CVE-2026-52918 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-52918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52918, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52918

Explore →

Is Your Infrastructure Affected by CVE-2026-52918?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs