CVE-2026-98108

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: 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 chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan

l2cap_new_connection() sets default value of channel mode to match the parent channel. l2cap_le_connect_req() left this at the default, and created L2CAP_MODE_EXT_FLOWCTL channels if listening pchan has that mode. This causes FLAG_DEFER_SETUP channels to reply to L2CAP_LE_CONN_REQ with L2CAP_ECRED_CONN_RSP, which is incorrect.

It can also result to stack OOB write (of l2cap_alloc_cid determined values) in l2cap_ecred_rsp_defer(), as l2cap_le_connect_req() does not limit maximum number of deferred channels or check for duplicate ident.

Fix by setting chan->mode correctly in l2cap_le_connect_req().

Also check channel mode in l2cap_ecred_rsp_defer(), and do WARN_ON_ONCE instead of OOB write to make it less brittle.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
38
EG Risk 38/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
Severity75% × 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.2%
EPSS %ILE
14th
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 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

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

Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6cb79e6499228cfdbd4b3301371ce74d01cd2f80
generic

Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d5a625cbc854d4c4f68e4b16fcf6e682d9a9ed1
generic

Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1074bcc57f741223f9fa82ce6afe5c3d783e4d10

Vendor Advisories for CVE-2026-98108(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 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-98108?
CVE-2026-98108 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix chan mode for LECONNREQ + EXT_FLOWCTL pchan l2capnewconnection() sets default value of channel mode to match the parent channel. l2capleconnect_req() left this at the default, and created L2CAPMODEEXT_FLOWCTL…
When was CVE-2026-98108 disclosed?
CVE-2026-98108 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98108 actively exploited?
CVE-2026-98108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98108?
CVE-2026-98108 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98108?
No fix for CVE-2026-98108 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-98108 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-98108

Explore →

Is Your Infrastructure Affected by CVE-2026-98108?

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

Book a Demo →Browse All CVEs