← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-43023

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-43023

Key Details

CVECVE-2026-43023
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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 (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-43023
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-43023
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.