CVE-2026-23461

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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: L2CAP: Fix use-after-free in l2cap_unregister_user

After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in hci_chan_del"), l2cap_conn_del() uses conn->lock to protect access to conn->users. However, l2cap_register_user() and l2cap_unregister_user() don't use conn->lock, creating a race condition where these functions can access conn->users and conn->hchan concurrently with l2cap_conn_del().

This can lead to use-after-free and list corruption bugs, as reported by syzbot.

Fix this by changing l2cap_register_user() and l2cap_unregister_user() to use conn->lock instead of hci_dev_lock(), ensuring consistent locking for the l2cap_conn structure.

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
16%
KEV
Not listed

Published

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/752a6c9596dd25efd6978a73ff21f3b592668f4a
generic

Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71030f3b3015a412133a805ff47970cdcf30c2b8
generic

Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11a87dd5df428a4b79a84d2790cac7f3c73f1f0d

Vendor Advisories for CVE-2026-23461(1)

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

Patch Availability(11)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (119 versions)6.19.10-1

Weakness Classification(1)

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

All Vendor Advisories

(13)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-23461?
CVE-2026-23461 is a high vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2capunregisteruser After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in hcichandel"), l2capconndel() uses conn->lock to protect access to conn->users. However,…
When was CVE-2026-23461 disclosed?
CVE-2026-23461 was first published in the National Vulnerability Database on April 3, 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-23461 actively exploited?
CVE-2026-23461 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 84.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23461?
CVE-2026-23461 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-23461?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23461, 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-23461

Explore →

Is Your Infrastructure Affected by CVE-2026-23461?

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