Local code execution via Bluetooth socket race
Published Jan 30, 2024 · Updated May 29, 2025
Use-after-free in Linux kernel Bluetooth code before 6.8-rc1 allows local users to execute code during Bluetooth pairing. bt_sock_poll passes a listening socket pointer to bt_accept_poll, which traverses accept_q after another task frees the socket. Triggering requires Bluetooth pairing and winning a nondeterministic concurrent race; the stale-pointer access can crash the kernel or enable code execution.
Summary
What happened
Use-after-free in Linux kernel Bluetooth code before 6.8-rc1 allows local users to execute code during Bluetooth pairing. bt_sock_poll passes a listening socket pointer to bt_accept_poll, which traverses accept_q after another task frees the socket. Triggering requires Bluetooth pairing and winning a nondeterministic concurrent race; the stale-pointer access can crash the kernel or enable code execution.
The record
- CVE
- CVE-2024-21803
- Published
- Jan 30, 2024
- Updated
- May 29, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2024CVE publishedPublication date reported by the CVE source.
- May 29, 2025Record 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=v2.6.12-rc2 <v6.8-rc1
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