[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-43023":6},{"stargazers_count":4,"fetched_at":5},8,"2026-09-19T04:32:17.889Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2026-43023","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                               \u003C- 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",null,[],[],[],[14],{"_key":15},"CVE-2026-43023",[],[],[],"2026-05-01T15:16:46.610Z","2026-06-15T19:06:24.661051977Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2026-43023",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},7.8,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",9.8,4.6,[40,60],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,50,54,57],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},"all",true,"ecosystem",{"version":51,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":52,"version_end_type":53,"fixed_in":9},"lt6_1_170_1","6.1.170-1","excluding",{"version":55,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":56,"version_end_type":53,"fixed_in":9},"lt6_12_85_1","6.12.85-1",{"version":58,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":59,"version_end_type":53,"fixed_in":9},"lt6_19_12_1","6.19.12-1",{"ecosystem":41,"name":61,"vendor":43,"product":61,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":61,"source":9,"versions":62},"linux-6.1",[63],{"version":64,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":65,"version_end_type":53,"fixed_in":9},"lt6_1_170_1~deb11u1","6.1.170-1~deb11u1"]