Kernel memory corruption via concurrent SCO connects
Published May 1, 2026 · Updated May 1, 2026
Race condition in Linux Kernel 6.3 and affected later branches allows local users to corrupt kernel memory through concurrent SCO connects. The sco_sock_connect() path reads sk_state and sk_type before taking the socket lock, so simultaneous connect() calls can attach a socket twice while an HCI disconnect closes it. Low-privilege local access and precise concurrency with a disconnect are required; later cleanup performs a double sock_put(), causing use-after-free and leaking the orphaned connection.
Summary
What happened
Race condition in Linux Kernel 6.3 and affected later branches allows local users to corrupt kernel memory through concurrent SCO connects. The sco_sock_connect() path reads sk_state and sk_type before taking the socket lock, so simultaneous connect() calls can attach a socket twice while an HCI disconnect closes it. Low-privilege local access and precise concurrency with a disconnect are required; later cleanup performs a double sock_put(), causing use-after-free and leaking the orphaned connection.
The record
- CVE
- CVE-2026-43023
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.3
- Affected versionversion=70a13b1e25fef37c87c8a1228ddb8900efbca7cf <dabf22269242e2f2bf44c43fcdc2fa763df7f9cc
- Affected versionversion=9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 <7e296ffdab5bdab718dff7c14288fdcb9154fa27
- Affected versionversion=9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 <8a5b0135d4a5d9683203a3d9a12a711ccec5936b
- Affected versionversion=9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 <98c8d3bfdaa657d8f472dbbebd7ea8cd816d8a8d
- Affected versionversion=9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 <adb90cd0f9f7a8d438fcb93354040fbafc5ae2a0
- Affected versionversion=9a8ec9e8ebb5a7c0cfbce2d6b4a6b67b2b78e8f3 <d002bd11024bd231bcb606877e33951ffb7bed14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo