CVE-2026-90091

HIGHPre-NVD 8.08.0—
EchelonGraph scoreHIGH confidence

Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 8.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.0Exploit: None knownExposed services: Not assessed

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

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan

For L2CAP sockets without owning sk->sk_socket, reading l2cap_pi(sk)->chan may race against concurrent l2cap_sock_kill() -> l2cap_sock_put_chan(). This excludes simultaneous proto_ops callbacks, but access in l2cap_sock_cleanup_listen() has unsafe lockless read.

[Task 1] [Task 2 (hdev->workqueue)] l2cap_sock_release(parent) l2cap_disconn_cfm l2cap_sock_cleanup_listen l2cap_conn_del bt_accept_dequeue l2cap_chan_del lock_sock(sk) l2cap_sock_teardown_cb bt_accept_unlink bt_sk(sk)->parent = NULL release_sock(sk) ----------------> lock_sock(sk) parent = /* NULL */ lock_sock(sk) <--------------------- release_sock(sk) sock_set_flag(sk, SOCK_ZAPPED) l2cap_sock_close_cb l2cap_sock_kill(sk) l2cap_sock_put_chan chan = READ l2cap_pi(sk)->chan l2cap_pi(sk)->chan = NULL l2cap_chan_hold_unless_zero l2cap_put_chan(chan) kref_get_unless_zero(&chan->ref)

Task 1 may observe NULL which causes null-ptr-deref.

Fix the race by taking lock_sock() in l2cap_sock_kill() to synchronize with l2cap_sock_cleanup_listen(). hold_unless_zero() is not needed here, l2cap_pi(sk)->chan owns reference if it is non-NULL.

Clarify code comments vs. locking.

CVSS v3
8.0
EG Score
8.0HIGHhigh confidence
EG Risk
41
EG Risk 41/100CISA SSVC

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
Severity80% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (6)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66d6ef18548ae6d7dd452b84115fc82c0a73a4ea
generic

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32a7bc6e93be36b37fe61f351d312d358195bd61
generic

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61d5ddbd524c715b224cbe7e9f01da4e05098b19
generic

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c7ac736b50fa259ed1bdddc18d79523f07c0442
generic

Bluetooth: L2CAP: fix race l2cap_sock_cleanup_listen() vs. put_chan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/827de6bd2865b22aaabd554540def3b8a33018ab

Vendor Advisories for CVE-2026-90091(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-90091?
CVE-2026-90091 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix race l2capsockcleanuplisten() vs. putchan For L2CAP sockets without owning sk->sk_socket, reading l2cappi(sk)->chan may race against concurrent l2capsock_kill() -> l2capsockputchan(). This excludes…
When was CVE-2026-90091 disclosed?
CVE-2026-90091 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90091 actively exploited?
CVE-2026-90091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90091?
CVE-2026-90091 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90091?
No fix for CVE-2026-90091 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90091 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-90091

Explore →

Is Your Infrastructure Affected by CVE-2026-90091?

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

Book a Demo →Browse All CVEs