Kernel memory corruption via missing driver allocation
Published Sep 30, 2024 · Updated Aug 5, 2026
Memory corruption in Linux 6.10 before 6.10.12 and 6.11 before 6.11.1 allows local users to crash the kernel during Bluetooth setup. The btintel_pcie probe path allocates hci_dev without reserving struct btintel_data, so later flag and pointer accesses run beyond that object. Reachability requires an Intel PCIe Bluetooth controller and local access to bring up or exercise its HCI device; corruption can panic the host or alter adjacent kernel objects.
Summary
What happened
Memory corruption in Linux 6.10 before 6.10.12 and 6.11 before 6.11.1 allows local users to crash the kernel during Bluetooth setup. The btintel_pcie probe path allocates hci_dev without reserving struct btintel_data, so later flag and pointer accesses run beyond that object. Reachability requires an Intel PCIe Bluetooth controller and local access to bring up or exercise its HCI device; corruption can panic the host or alter adjacent kernel objects.
The record
- CVE
- CVE-2024-46869
- Published
- Sep 30, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.10
- Affected versionversion=6e65a09f927566f257322358d429b267548473eb <2b4545f08cc68d2fc835f5c490b36e0264750030
- Affected versionversion=6e65a09f927566f257322358d429b267548473eb <7ffaa200251871980af12e57649ad57c70bf0f43
- Affected versionversion=6e65a09f927566f257322358d429b267548473eb <fa9e1c1b1f389a8e6d987ac6cb3e2ba04f8ec875
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