CVE-2026-80666

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week

Also known asEUVD-2026-67542 (ENISA EUVD) · GHSA-53mq-p582-hhfx (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: sco: Fix a race condition in sco_sock_timeout()

sco_sock_timeout() runs asynchronously and lock_sock(sk). If the socket is closing while the timer is running, it holds the same lock (lock_sock(sk)) twice, leading to a deadlock.

CPU 0 CPU 1 ==================== ====================== sco_sock_close() sco_sock_timeout() lock_sock(sk) // <-- LOCK __sco_sock_close() sco_chan_del() sco_conn_put() sco_conn_free() disable_delayed_work_sync() lock(sk) // <-- SAME LOCK

Fix this by moving disable_delayed_work_sync() outside of lock_sock(sk), ensuring that no lock_sock(sk) is held before sco_sock_timeout().

Lockdep splat:

WARNING: possible circular locking dependency detected 6.13.0-rc4 #7 Not tainted

syz-executor292/9514 is trying to acquire lock: ffff8881115d5070 ((work_completion)(&(&conn->timeout_work)->work)){+.+.}-{0:0}, at: rcu_lock_acquire sect/v6.13-rc4/./include/linux/rcupdate.h:337 [inline] ffff8881115d5070 ((work_completion)(&(&conn->timeout_work)->work)){+.+.}-{0:0}, at: rcu_read_lock sect/v6.13-rc4/./include/linux/rcupdate.h:849 [inline] ffff8881115d5070 ((work_completion)(&(&conn->timeout_work)->work)){+.+.}-{0:0}, at: start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4137 [inline] ffff8881115d5070 ((work_completion)(&(&conn->timeout_work)->work)){+.+.}-{0:0}, at: __flush_work+0xd1/0xc40 sect/v6.13-rc4/kernel/workqueue.c:4195

but task is already holding lock: ffff88807db3a258 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock sect/v6.13-rc4/./include/net/sock.h:1623 [inline] ffff88807db3a258 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_sock_close+0x25/0x100 sect/v6.13-rc4/net/bluetooth/sco.c:524

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}: lock_acquire+0x1c4/0x520 sect/v6.13-rc4/kernel/locking/lockdep.c:5849 lock_sock_nested+0x48/0x130 sect/v6.13-rc4/net/core/sock.c:3622 lock_sock sect/v6.13-rc4/./include/net/sock.h:1623 [inline] sco_sock_timeout+0xbe/0x270 sect/v6.13-rc4/net/bluetooth/sco.c:158 process_one_work sect/v6.13-rc4/kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa99/0x18f0 sect/v6.13-rc4/kernel/workqueue.c:3310 worker_thread+0x8a9/0xd80 sect/v6.13-rc4/kernel/workqueue.c:3391 kthread+0x2c6/0x360 sect/v6.13-rc4/kernel/kthread.c:389 ret_from_fork+0x4e/0x80 sect/v6.13-rc4/arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 sect/v6.13-rc4/arch/x86/entry/entry_64.S:244

-> #0 ((work_completion)(&(&conn->timeout_work)->work)){+.+.}-{0:0}: check_prev_add sect/v6.13-rc4/kernel/locking/lockdep.c:3161 [inline] check_prevs_add sect/v6.13-rc4/kernel/locking/lockdep.c:3280 [inline] validate_chain+0x1888/0x5760 sect/v6.13-rc4/kernel/locking/lockdep.c:3904 __lock_acquire+0x13b4/0x2120 sect/v6.13-rc4/kernel/locking/lockdep.c:5226 lock_acquire+0x1c4/0x520 sect/v6.13-rc4/kernel/locking/lockdep.c:5849 touch_work_lockdep_map sect/v6.13-rc4/kernel/workqueue.c:3909 [inline] start_flush_work sect/v6.13-rc4/kernel/workqueue.c:4163 [inline] __flush_work+0x70f/0xc40 sect/v6.13-rc4/kernel/workqueue.c:4195 __cancel_work_sync sect/v6.13-rc4/kernel/workqueue.c:4351 [inline] disable_delayed_work_sync+0xbb/0xf0 sect/v6.13-rc4/kernel/workqueue.c:4514 sco_conn_free sect/v6.13-rc4/net/bluetooth/sco.c:95 [inline] kref_put sect/v6.13-rc4/./include/linux/kref.h:65 [inline] sco_conn_put+0x18f/0x270 sect/v6.13-rc4/net/bluetooth/sco.c:107 sco_chan_del+0xe2/0x210 sect/v6.13-rc4/net/bluetooth/sco.c:236 sco_sock_close+0x8f/0x100 sect/v6.13-rc4/net/bluetooth/sco.c:526 sco_sock_release+0x62/0x2d0 sect/v6.13-rc4/net/blueto ---truncated---

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

August 28, 2026

References (3)

Vendor Advisories for CVE-2026-80666(1)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-29ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-29ubuntu
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-29ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-29ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-29ubuntu
linuxKernel @ 6.18.40 (fixes >=6.13.0)—osv

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 87 are merged into the row they repeat.

  1. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-29 17:41 UTCEG score recompute
  3. 2026-10-29 17:41 UTCVendor advisory
  4. 2026-10-29 17:41 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-27 04:25 UTCOSV refresh
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-25 13:59 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-18 03:10 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 58 more
  1. 2026-10-12 14:57 UTCEG score recompute
  2. 2026-10-11 19:21 UTCEG score recompute
  3. 2026-10-11 16:37 UTCEG score recompute
  4. 2026-10-11 13:55 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-08 06:45 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-05 03:41 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-02 00:38 UTCEG score recompute
  18. 2026-10-02 00:38 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-28 21:10 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  22. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-25 15:42 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  27. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-22 12:02 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  31. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-19 09:01 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  34. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-16 05:55 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  37. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-09-13 02:55 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  40. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  41. 2026-09-09 23:54 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  42. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-09-06 17:32 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  44. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  46. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  47. 2026-09-03 14:31 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  48. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  49. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  50. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  51. 2026-08-31 11:28 UTCEG score recompute
  52. 2026-08-31 11:28 UTCGHSA enrichmentGHSA-53mq-p582-hhfx
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-08-28 08:20 UTCNVD update
  57. 2026-08-28 07:34 UTCEG score recompute
  58. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-80666?
CVE-2026-80666 is a vulnerability whose severity is not yet rated; its CVE record was published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: sco: Fix a race condition in scosocktimeout() scosocktimeout() runs asynchronously and lock_sock(sk). If the socket is closing while the timer is running, it holds the same lock (lock_sock(sk)) twice, leading to a…
When was the CVE record for CVE-2026-80666 published?
The CVE record for CVE-2026-80666 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-80666 actively exploited?
CVE-2026-80666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80666?
A fix for CVE-2026-80666 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80666 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-80666

Explore →

Is Your Infrastructure Affected by CVE-2026-80666?

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

Book a Demo →Browse All CVEs