Kernel crash via unchecked pairing allocation failure
Published Aug 26, 2024 · Updated May 11, 2026
NULL pointer dereference in Linux 4.3 through 6.11-rc4 allows local users to crash the kernel through Bluetooth device pairing. When hci_conn_params_add returns NULL during Low Energy pairing, pair_device dereferences p->auto_connect instead of handling the allocation failure. The path requires local access to issue a Bluetooth management pairing command and an allocation failure; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in Linux 4.3 through 6.11-rc4 allows local users to crash the kernel through Bluetooth device pairing. When hci_conn_params_add returns NULL during Low Energy pairing, pair_device dereferences p->auto_connect instead of handling the allocation failure. The path requires local access to issue a Bluetooth management pairing command and an allocation failure; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2024-43884
- Published
- Aug 26, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.3
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <064dd929c76532359d2905d90a7c12348043cfd4
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <11b4b0e63f2621b33b2e107407a7d67a65994ca1
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <538fd3921afac97158d4177139a0ad39f056dbb2
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <5da2884292329bc9be32a7778e0e119f06abe503
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <90e1ff1c15e5a8f3023ca8266e3a85869ed03ee9
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <951d6cb5eaac5130d076c728f2a6db420621afdb
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <9df9783bd85610d3d6e126a1aca221531f6f6dcb
- Affected versionversion=5157b8a503fa834e8569c7fed06981e3d3d53db0 <ee0799103b1ae4bcfd80dc11a15df085f6ee1b61
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