CVE-2026-52918

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 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(3)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 86× 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.

Showing the most recent 100 of 308 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:22 UTCEG score recompute
  11. 2026-08-30 20:22 UTCVendor advisory
  12. 2026-08-30 20:22 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 04:56 UTCEG score recompute
  17. 2026-08-28 04:56 UTCVendor advisory
  18. 2026-08-28 04:56 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 01:05 UTCEG score recompute
  23. 2026-08-25 01:05 UTCVendor advisory
  24. 2026-08-25 01:05 UTCGHSA enrichment
  25. 2026-08-24 13:52 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:52 UTCVendor advisory
  2. 2026-08-24 13:52 UTCGHSA enrichment
  3. 2026-08-23 23:24 UTCVendor advisory
  4. 2026-08-23 23:24 UTCGHSA enrichment
  5. 2026-08-23 12:11 UTCVendor advisory
  6. 2026-08-23 12:11 UTCGHSA enrichment
  7. 2026-08-23 00:59 UTCEG score recompute
  8. 2026-08-23 00:59 UTCVendor advisory
  9. 2026-08-23 00:59 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 13:26 UTCEG score recompute
  12. 2026-08-22 13:26 UTCVendor advisory
  13. 2026-08-22 13:26 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 17:30 UTCVendor advisory
  16. 2026-08-21 17:30 UTCGHSA enrichment
  17. 2026-08-21 06:14 UTCEG score recompute
  18. 2026-08-21 06:14 UTCVendor advisory
  19. 2026-08-21 06:14 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 18:53 UTCVendor advisory
  22. 2026-08-20 18:53 UTCGHSA enrichment
  23. 2026-08-20 07:40 UTCEG score recompute
  24. 2026-08-20 07:40 UTCVendor advisory
  25. 2026-08-20 07:40 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 15:37 UTCVendor advisory
  28. 2026-08-19 15:37 UTCGHSA enrichment
  29. 2026-08-19 04:00 UTCEG score recompute
  30. 2026-08-19 04:00 UTCVendor advisory
  31. 2026-08-19 04:00 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 07:21 UTCVendor advisory
  35. 2026-08-17 07:21 UTCGHSA enrichment
  36. 2026-08-16 20:09 UTCEG score recompute
  37. 2026-08-16 20:09 UTCVendor advisory
  38. 2026-08-16 20:09 UTCGHSA enrichment
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 08:00 UTCEG score recompute
  41. 2026-08-16 08:00 UTCVendor advisory
  42. 2026-08-16 08:00 UTCGHSA enrichment
  43. 2026-08-16 02:14 UTCEPSS rescore
  44. 2026-08-15 20:48 UTCVendor advisory
  45. 2026-08-15 20:48 UTCGHSA enrichment
  46. 2026-08-15 09:32 UTCEG score recompute
  47. 2026-08-15 09:32 UTCVendor advisory
  48. 2026-08-15 09:32 UTCGHSA enrichment
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 22:19 UTCVendor advisory
  51. 2026-08-14 22:19 UTCGHSA enrichment
  52. 2026-08-14 11:06 UTCVendor advisory
  53. 2026-08-14 11:06 UTCGHSA enrichment
  54. 2026-08-13 23:54 UTCEG score recompute
  55. 2026-08-13 23:54 UTCVendor advisory
  56. 2026-08-13 23:54 UTCGHSA enrichment
  57. 2026-08-13 22:00 UTCEPSS rescore
  58. 2026-08-13 12:41 UTCVendor advisory
  59. 2026-08-13 12:41 UTCGHSA enrichment
  60. 2026-08-13 01:24 UTCVendor advisory
  61. 2026-08-13 01:24 UTCGHSA enrichment
  62. 2026-08-12 14:11 UTCEG score recompute
  63. 2026-08-12 14:11 UTCVendor advisory
  64. 2026-08-12 14:11 UTCGHSA enrichment
  65. 2026-08-12 13:51 UTCEPSS rescore
  66. 2026-08-12 02:58 UTCVendor advisory
  67. 2026-08-12 02:58 UTCGHSA enrichment
  68. 2026-08-11 15:46 UTCEG score recompute
  69. 2026-08-11 15:46 UTCVendor advisory
  70. 2026-08-11 15:46 UTCGHSA enrichment
  71. 2026-08-11 04:34 UTCEG score recompute
  72. 2026-08-11 04:34 UTCVendor advisory
  73. 2026-08-11 04:34 UTCGHSA enrichment
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 17:21 UTCVendor advisory

Related CVEs(same vendor)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 82.0% of all scored CVEs.
What is the CVSS score of CVE-2026-52918?
CVE-2026-52918 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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