System crash via unfinished Bluetooth SDIO work
Published Apr 11, 2023 · Updated Aug 26, 2024
Use-after-free in the Linux kernel before 6.3-rc4 allows attackers to crash the system through the Bluetooth HCI SDIO driver. The btsdio_send_frame path schedules data->work, while btsdio_remove tears down hdev without first canceling unfinished work. Reaching the race requires root-level driver removal or physical access; the grounded consequence is a system crash.
Summary
What happened
Use-after-free in the Linux kernel before 6.3-rc4 allows attackers to crash the system through the Bluetooth HCI SDIO driver. The btsdio_send_frame path schedules data->work, while btsdio_remove tears down hdev without first canceling unfinished work. Reaching the race requires root-level driver removal or physical access; the grounded consequence is a system crash.
The record
- CVE
- CVE-2023-1989
- Published
- Apr 11, 2023
- Updated
- Aug 26, 2024
- Vendor
- Debian
- Product
- Debian GNU/Linux
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Aug 26, 2024Record 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=5.10.178-3
What conditions does exploitation require?
What is affected?
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