System crash via unlocked Bluetooth key-size validation
Published Feb 5, 2024 · Updated Feb 13, 2025
Race condition in Linux Kernel 5.6-rc1 through 6.7.2 allows local users to cause a system crash through Bluetooth debugfs. The min_key_size_set and max_key_size_set functions validate against the paired limit before acquiring hci_dev_lock, so concurrent writes can store a maximum below the minimum. The setters require privileged local debugfs access, and the reported null-pointer dereference can panic the kernel; upstream runtime triggering was not tested.
Summary
What happened
Race condition in Linux Kernel 5.6-rc1 through 6.7.2 allows local users to cause a system crash through Bluetooth debugfs. The min_key_size_set and max_key_size_set functions validate against the paired limit before acquiring hci_dev_lock, so concurrent writes can store a maximum below the minimum. The setters require privileged local debugfs access, and the reported null-pointer dereference can panic the kernel; upstream runtime triggering was not tested.
The record
- CVE
- CVE-2024-24860
- Published
- Feb 5, 2024
- Updated
- Feb 13, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, CWE-362, CAPEC-26, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=v5.6-rc1 <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