CVE-2026-53071

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 — 3 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: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp

l2cap_ecred_reconf_rsp() calls l2cap_chan_del() without holding l2cap_chan_lock(). Every other l2cap_chan_del() caller in the file acquires the lock first. A remote BLE device can send a crafted L2CAP ECRED reconfiguration response to corrupt the channel list while another thread is iterating it.

Add l2cap_chan_hold() and l2cap_chan_lock() before l2cap_chan_del(), and l2cap_chan_unlock() and l2cap_chan_put() after, matching the pattern used in l2cap_ecred_conn_rsp() and l2cap_conn_del().

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

Published

June 24, 2026

Last Modified

July 22, 2026

Advisory Details (8)

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

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96dca51715d86559ed6ed8028e5445cecb80f3ae
generic

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77a853aec710b2fdf41fa298ea3cbc9a4358f917
generic

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5501d055a1ce3c747141e3955ba8cf034d193f3e
generic

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42776497cdbc9a665b384a6dcb85f0d4bd927eab
generic

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/330b20ec97916961ee0e6c29c06bc0fa7c96e64c
generic

Bluetooth: l2cap: Add missing chan lock in l2cap_ecred_reconf_rsp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ccd75c51f620374086f359e906917676e699a1c

Vendor Advisories for CVE-2026-53071(3)

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

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 87× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 03:39 UTCVendor advisory
  8. 2026-07-17 03:38 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 15:05 UTCVendor advisory
  11. 2026-07-16 15:05 UTCGHSA enrichment
  12. 2026-07-16 02:31 UTCVendor advisory
  13. 2026-07-16 02:31 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 13:59 UTCVendor advisory
  17. 2026-07-15 13:59 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 00:50 UTCVendor advisory
  21. 2026-07-15 00:50 UTCGHSA enrichment
  22. 2026-07-14 12:16 UTCVendor advisory
  23. 2026-07-14 12:16 UTCGHSA enrichment
  24. 2026-07-13 23:44 UTCGHSA enrichment
  25. 2026-07-13 22:31 UTCEPSS rescore
Show 62 more
  1. 2026-07-13 11:12 UTCGHSA enrichment
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 22:39 UTCVendor advisory
  5. 2026-07-12 22:39 UTCGHSA enrichment
  6. 2026-07-12 10:07 UTCVendor advisory
  7. 2026-07-12 10:07 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 21:33 UTCVendor advisory
  10. 2026-07-11 21:33 UTCGHSA enrichment
  11. 2026-07-11 09:01 UTCVendor advisory
  12. 2026-07-11 09:01 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-10 20:29 UTCVendor advisory
  16. 2026-07-10 20:29 UTCGHSA enrichment
  17. 2026-07-10 07:56 UTCVendor advisory
  18. 2026-07-10 07:56 UTCGHSA enrichment
  19. 2026-07-09 19:12 UTCGHSA enrichment
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 06:31 UTCGHSA enrichment
  23. 2026-07-08 17:58 UTCGHSA enrichment
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 15:16 UTCEPSS rescore
  26. 2026-07-08 05:27 UTCGHSA enrichment
  27. 2026-07-07 16:54 UTCGHSA enrichment
  28. 2026-07-07 13:46 UTCEPSS rescore
  29. 2026-07-07 13:46 UTCEPSS rescore
  30. 2026-07-07 02:43 UTCGHSA enrichment
  31. 2026-07-06 14:10 UTCGHSA enrichment
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-06 02:23 UTCEPSS rescore
  34. 2026-07-06 01:37 UTCGHSA enrichment
  35. 2026-07-05 13:04 UTCGHSA enrichment
  36. 2026-07-05 02:31 UTCEPSS rescore
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-05 00:31 UTCGHSA enrichment
  39. 2026-07-04 11:59 UTCGHSA enrichment
  40. 2026-07-04 06:31 UTCEPSS rescore
  41. 2026-07-03 23:26 UTCGHSA enrichment
  42. 2026-07-03 10:54 UTCGHSA enrichment
  43. 2026-07-02 22:20 UTCGHSA enrichment
  44. 2026-07-02 09:48 UTCGHSA enrichment
  45. 2026-07-01 21:16 UTCGHSA enrichment
  46. 2026-07-01 15:07 UTCEPSS rescore
  47. 2026-07-01 08:44 UTCGHSA enrichment
  48. 2026-06-30 23:22 UTCEPSS rescore
  49. 2026-06-30 20:11 UTCGHSA enrichment
  50. 2026-06-30 07:39 UTCEG score recompute▲ 8.80
  51. 2026-06-30 07:39 UTCGHSA enrichment
  52. 2026-06-29 14:06 UTCEPSS rescore
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-28 14:07 UTCEPSS rescore
  55. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  56. 2026-06-28 04:56 UTCEPSS rescore
  57. 2026-06-28 04:56 UTCEPSS rescore
  58. 2026-06-27 12:57 UTCGHSA enrichment
  59. 2026-06-27 03:08 UTCEPSS rescore
  60. 2026-06-25 13:49 UTCEPSS rescore
  61. 2026-06-24 18:15 UTCEG score recompute
  62. 2026-06-24 18:03 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53071?
CVE-2026-53071 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: l2cap: Add missing chan lock in l2capecredreconf_rsp l2capecredreconfrsp() calls l2capchan_del() without holding l2capchanlock(). Every other l2capchandel() caller in the file acquires the lock first. A remote BLE device…
When was CVE-2026-53071 disclosed?
CVE-2026-53071 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53071 actively exploited?
CVE-2026-53071 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-53071?
CVE-2026-53071 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53071, 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-53071

Explore →

Is Your Infrastructure Affected by CVE-2026-53071?

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

Start Free Scan →Browse All CVEs