CVE-2026-53071

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM 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
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.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
44
EG Risk 44/100

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%
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

Published

June 24, 2026

Last Modified

September 16, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
Patch available.
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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-23ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-09-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-23ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-23ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-09-23ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-23ubuntu
redhatkernel-0:5.14.0-284.191.1.el9_22026-09-16redhat
redhatkernel-rt-0:5.14.0-284.191.1.rt14.476.el9_22026-09-16redhat
redhatkernel-0:4.18.0-372.213.1.el8_62026-09-09redhat
redhatkernel-0:4.18.0-305.206.1.el8_42026-09-09redhat
redhatkernel-0:5.14.0-687.29.1.el9_82026-07-22redhat
redhatkernel-rt-0:4.18.0-553.146.1.rt7.487.el8_102026-07-21redhat
redhatkernel-0:6.12.0-211.37.1.el10_22026-07-21redhat
redhatkernel-0:4.18.0-553.146.1.el8_102026-07-21redhat

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 rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(3)

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

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 7× in last 7d / 43× 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 323 total refreshes for this CVE.

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

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 on June 24, 2026, with the most recent update on September 16, 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 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53071?
CVE-2026-53071 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53071?
A fix for CVE-2026-53071 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53071 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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