Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43023: Bluetooth: SCO: fix race conditions in sco_sock_connect()

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 6.1.168, 7e296ffdab5bdab718dff7c14288fdcb9154fa27, 8a5b0135d4a5d9683203a3d9a12a711ccec5936b.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 6.1.168, 7e296ffdab5bdab718dff7c14288fdcb9154fa27, 8a5b0135d4a5d9683203a3d9a12a711ccec5936b or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

Published
May 1, 2026
Updated
Nov 11, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43023

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.3affected
    • 70a13b1e25fef37c87c8a1228ddb8900efbca7cf and later · before dabf22269242e2f2bf44c43fcdc2fa763df7f9ccaffected · git
    • 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 and later · before adb90cd0f9f7a8d438fcb93354040fbafc5ae2a0affected · git
    • 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 and later · before 7e296ffdab5bdab718dff7c14288fdcb9154fa27affected · git
    • 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 and later · before 98c8d3bfdaa657d8f472dbbebd7ea8cd816d8a8daffected · git
    • 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 and later · before d002bd11024bd231bcb606877e33951ffb7bed14affected · git
    • 9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 and later · before 8a5b0135d4a5d9683203a3d9a12a711ccec5936baffected · git
    • 6.1.109 and later · before 6.1.168affected · semver
    • before 6.3not affected · semver
    • 6.1.168 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.18.1.el10_26.12.0-211.18.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43021May 1, 2026 · Bluetooth: hci_sync: fix leaks when hci_cmd_sync_queue_once fails
    22Monitor
  • ← EarlierCVE-2026-43022May 1, 2026 · Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists
    22Monitor
  • Later →CVE-2026-43024May 1, 2026 · netfilter: nf_tables: reject immediate NF_QUEUE verdict
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux6.1.168Vendor (CNA)
Linux Linux7e296ffdab5bdab718dff7c14288fdcb9154fa27Vendor (CNA)
Linux Linux8a5b0135d4a5d9683203a3d9a12a711ccec5936bVendor (CNA)
Linux Linux98c8d3bfdaa657d8f472dbbebd7ea8cd816d8a8dVendor (CNA)
Linux Linuxadb90cd0f9f7a8d438fcb93354040fbafc5ae2a0Vendor (CNA)
Linux Linuxd002bd11024bd231bcb606877e33951ffb7bed14Vendor (CNA)
Linux Linuxdabf22269242e2f2bf44c43fcdc2fa763df7f9ccVendor (CNA)
almalinux:kernel5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.12.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+12

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

All records