CVE-2026-90092

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: reject accept queue add unless BT_LISTEN

New sk should not be added to parent socket accept queue after last l2cap_sock_cleanup_listen() has run in l2cap_sock_teardown_cb() and state set to BT_CLOSED, as that can result to UAF on dereferencing the dangling parent reference.

l2cap_sock_new_connection_cb() may race with parent l2cap_chan teardown, due to chan->state accessed without consistent locking:

[Task 1] [Task 2] l2cap_sock_release(parent) l2cap_connect l2cap_sock_shutdown pchan = l2cap_global_chan_by_psm l2cap_chan_lock(pchan) l2cap_chan_close l2cap_sock_teardown_cb pchan->state = BT_CLOSED l2cap_chan_unlock(pchan) ------> l2cap_chan_lock(pchan) l2cap_new_connection l2cap_sock_new_connection_cb l2cap_chan_lock(pchan) <-------- l2cap_chan_unlock(pchan) l2cap_sock_kill(parent) /* bt_sk(sk)->parent dangling */

Fix by adding check for sk_state == BT_LISTEN after acquiring sk lock in l2cap_sock_new_connection_cb(). Add lock_sock() around sk_state writes where missing, to avoid data races.

Although the data races on pchan->state should be fixed too, this defensive sk_state check probably makes sense in any case.

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: reject accept queue add unless BT_LISTEN - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87276dc15b559d32757a43b4415c8445fbae06c4
generic

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a3a27aaf19bf069720e024ce6fde54e6bf80df9
generic

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/491e4c60017969b053888029998d2a61f298986a
generic

Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf61a65c6093970e3b50031c4b79ebf3bd411eba

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

Frequently asked(5)

What is CVE-2026-90092?
CVE-2026-90092 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN New sk should not be added to parent socket accept queue after last l2capsockcleanuplisten() has run in l2capsockteardowncb() and state set to BT_CLOSED, as that can result…
When was CVE-2026-90092 disclosed?
CVE-2026-90092 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-90092 actively exploited?
CVE-2026-90092 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-90092?
CVE-2026-90092 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-90092?
No fix for CVE-2026-90092 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-90092 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-90092

Explore →

Is Your Infrastructure Affected by CVE-2026-90092?

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

Book a Demo →Browse All CVEs