CVE-2026-43023

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

Bluetooth: SCO: fix race conditions in sco_sock_connect()

sco_sock_connect() checks sk_state and sk_type without holding the socket lock. Two concurrent connect() syscalls on the same socket can both pass the check and enter sco_connect(), leading to use-after-free.

The buggy scenario involves three participants and was confirmed with additional logging instrumentation:

Thread A (connect): HCI disconnect: Thread B (connect):

sco_sock_connect(sk) sco_sock_connect(sk) sk_state==BT_OPEN sk_state==BT_OPEN (pass, no lock) (pass, no lock) sco_connect(sk): sco_connect(sk): hci_dev_lock hci_dev_lock hci_connect_sco <- blocked -> hcon1 sco_conn_add->conn1 lock_sock(sk) sco_chan_add: conn1->sk = sk sk->conn = conn1 sk_state=BT_CONNECT release_sock hci_dev_unlock hci_dev_lock sco_conn_del: lock_sock(sk) sco_chan_del: sk->conn=NULL conn1->sk=NULL sk_state= BT_CLOSED SOCK_ZAPPED release_sock hci_dev_unlock (unblocked) hci_connect_sco -> hcon2 sco_conn_add -> conn2 lock_sock(sk) sco_chan_add: sk->conn=conn2 sk_state= BT_CONNECT // zombie sk! release_sock hci_dev_unlock

Thread B revives a BT_CLOSED + SOCK_ZAPPED socket back to BT_CONNECT. Subsequent cleanup triggers double sock_put() and use-after-free. Meanwhile conn1 is leaked as it was orphaned when sco_conn_del() cleared the association.

Fix this by:

  • Moving lock_sock() before the sk_state/sk_type checks in
sco_sock_connect() to serialize concurrent connect attempts
  • Fixing the sk_type != SOCK_SEQPACKET check to actually
return the error instead of just assigning it
  • Adding a state re-check in sco_connect() after lock_sock()
to catch state changes during the window between the locks
  • Adding sco_pi(sk)->conn check in sco_chan_add() to prevent
double-attach of a socket to multiple connections
  • Adding hci_conn_drop() on sco_chan_add failure to prevent
HCI connection leaks

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
0.9%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 8, 2026

Advisory Details (6)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

Bluetooth: SCO: fix race conditions in sco_sock_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: fix race conditions in sco_sock_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: fix race conditions in sco_sock_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: SCO: fix race conditions in sco_sock_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98c8d3bfdaa657d8f472dbbebd7ea8cd816d8a8d
generic

Bluetooth: SCO: fix race conditions in sco_sock_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a5b0135d4a5d9683203a3d9a12a711ccec5936b
generic

Bluetooth: SCO: fix race conditions in sco_sock_connect() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e296ffdab5bdab718dff7c14288fdcb9154fa27

Vendor Advisories for CVE-2026-43023(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
linuxKernel @ 6.1.168—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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× 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.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-20 12:02 UTCOSV refresh
  4. 2026-07-16 17:03 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-19 19:25 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-15 17:49 UTCEPSS rescore
  6. 2026-06-14 21:53 UTCVendor advisory
  7. 2026-06-14 21:53 UTCGHSA enrichment
  8. 2026-06-14 08:51 UTCVendor advisory
  9. 2026-06-14 08:51 UTCGHSA enrichment
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 10:21 UTCVendor advisory
  14. 2026-06-12 10:21 UTCGHSA enrichment
  15. 2026-06-11 20:03 UTCVendor advisory
  16. 2026-06-11 20:02 UTCGHSA enrichment
  17. 2026-06-11 14:00 UTCEPSS rescore
  18. 2026-06-11 06:57 UTCVendor advisory
  19. 2026-06-11 06:57 UTCGHSA enrichment
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 17:55 UTCVendor advisory
  22. 2026-06-10 17:55 UTCGHSA enrichment
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-10 04:53 UTCVendor advisory
  26. 2026-06-10 04:53 UTCGHSA enrichment
  27. 2026-06-09 15:51 UTCVendor advisory
  28. 2026-06-09 15:51 UTCGHSA enrichment
  29. 2026-06-09 02:49 UTCVendor advisory
  30. 2026-06-09 02:49 UTCGHSA enrichment
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-08 14:17 UTCEPSS rescore
  33. 2026-06-08 12:48 UTCVendor advisory
  34. 2026-06-08 12:48 UTCGHSA enrichment
  35. 2026-06-07 23:45 UTCVendor advisory
  36. 2026-06-07 23:45 UTCGHSA enrichment
  37. 2026-06-07 15:25 UTCEPSS rescore
  38. 2026-06-07 15:25 UTCEPSS rescore
  39. 2026-06-07 10:34 UTCVendor advisory
  40. 2026-06-07 10:34 UTCGHSA enrichment
  41. 2026-06-06 21:32 UTCVendor advisory
  42. 2026-06-06 21:32 UTCGHSA enrichment
  43. 2026-06-06 13:47 UTCEPSS rescore
  44. 2026-06-06 13:47 UTCEPSS rescore
  45. 2026-06-06 07:45 UTCVendor advisory
  46. 2026-06-06 07:45 UTCGHSA enrichment
  47. 2026-06-05 22:47 UTCEPSS rescore
  48. 2026-06-05 18:42 UTCVendor advisory
  49. 2026-06-05 18:42 UTCGHSA enrichment
  50. 2026-06-05 06:10 UTCEPSS rescore
  51. 2026-06-05 06:10 UTCEPSS rescore
  52. 2026-06-05 05:40 UTCVendor advisory
  53. 2026-06-05 05:40 UTCGHSA enrichment
  54. 2026-06-04 16:38 UTCVendor advisory
  55. 2026-06-04 16:38 UTCGHSA enrichment
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 03:36 UTCVendor advisory
  59. 2026-06-04 03:36 UTCGHSA enrichment
  60. 2026-06-03 14:34 UTCVendor advisory
  61. 2026-06-03 14:34 UTCGHSA enrichment
  62. 2026-06-03 01:31 UTCVendor advisory
  63. 2026-06-03 01:31 UTCGHSA enrichment
  64. 2026-06-02 20:13 UTCEPSS rescore
  65. 2026-06-02 12:28 UTCVendor advisory
  66. 2026-06-02 12:28 UTCGHSA enrichment
  67. 2026-06-01 23:25 UTCVendor advisory
  68. 2026-06-01 23:25 UTCGHSA enrichment
  69. 2026-06-01 13:52 UTCEPSS rescore
  70. 2026-06-01 13:52 UTCEPSS rescore
  71. 2026-06-01 10:21 UTCVendor advisory
  72. 2026-06-01 10:21 UTCGHSA enrichment
  73. 2026-05-31 22:30 UTCEPSS rescore
  74. 2026-05-31 22:30 UTCEPSS rescore
  75. 2026-05-31 00:16 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43023?
CVE-2026-43023 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: fix race conditions in scosockconnect() scosockconnect() checks skstate and sktype without holding the socket lock. Two concurrent connect() syscalls on the same socket can both pass the check and enter…
When was CVE-2026-43023 disclosed?
CVE-2026-43023 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43023 actively exploited?
CVE-2026-43023 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43023?
CVE-2026-43023 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43023?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43023, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43023

Explore →

Is Your Infrastructure Affected by CVE-2026-43023?

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

Start Free Scan →Browse All CVEs