CVE-2026-89774

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
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.8Exploit: 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: SCO: hold sk properly in sco_conn_ready

sk deref in sco_conn_ready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk and parent sk is currently accessed without either, and without checking parent->sk_state:

[Task 1] [Task 2] sco_sock_release sco_conn_ready sk = conn->sk lock_sock(sk) conn->sk = NULL lock_sock(sk) release_sock(sk) sco_sock_kill(sk) UAF on sk deref

and similarly for access to sco_get_sock_listen() return value.

Fix possible UAF by holding sk refcount in sco_conn_ready() and making sco_get_sock_listen() increase refcount. Also recheck after lock_sock that the socket is still valid. Adjust conn->sk locking so it's protected also by lock_sock() of the associated socket if any.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/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
Severity88% × 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
32nd
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 16, 2026

Last Modified

September 16, 2026

Advisory Details (6)

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

Bluetooth: SCO: hold sk properly in sco_conn_ready - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: hold sk properly in sco_conn_ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7199c78c3a3e399a4dc439d845826793880ccedc
generic

Bluetooth: SCO: hold sk properly in sco_conn_ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73cb063f5ec6ca51eb1e246c6d332563002ac277
generic

Bluetooth: SCO: hold sk properly in sco_conn_ready - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: hold sk properly in sco_conn_ready - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: hold sk properly in sco_conn_ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50aae396dc30377bec8e3b181b8346f8fd38f7d8

Vendor Advisories for CVE-2026-89774(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)
  • every version up to 7.1.3-1: fixed in 7.1.3-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-89774?
CVE-2026-89774 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: hold sk properly in scoconnready sk deref in scoconnready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk and parent sk is currently accessed without either, and…
When was CVE-2026-89774 disclosed?
CVE-2026-89774 was first published 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-89774 actively exploited?
CVE-2026-89774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89774?
CVE-2026-89774 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-89774?
No fix for CVE-2026-89774 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-89774 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-89774

Explore →

Is Your Infrastructure Affected by CVE-2026-89774?

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

Book a Demo →Browse All CVEs