System crash via L2CAP channel deletion race
Published May 13, 2024 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernel releases beginning with 3.4 allows local users to crash the kernel through Bluetooth L2CAP activity. A race lets l2cap_chan_del() clear chan->conn while l2cap_chan_timeout() subsequently dereferences that pointer when locking the connection. A low-privileged local context and the affected Bluetooth path are required; successful triggering causes a kernel Oops and service interruption.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases beginning with 3.4 allows local users to crash the kernel through Bluetooth L2CAP activity. A race lets l2cap_chan_del() clear chan->conn while l2cap_chan_timeout() subsequently dereferences that pointer when locking the connection. A low-privileged local context and the affected Bluetooth path are required; successful triggering causes a kernel Oops and service interruption.
The record
- CVE
- CVE-2024-27399
- Published
- May 13, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 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=3.4
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <06acb75e7ed600d0bbf7bff5628aa8f24a97978c
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <6466ee65e5b27161c846c73ef407f49dfa1bd1d9
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <8960ff650aec70485b40771cd8e6e8c4cb467d33
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <955b5b6c54d95b5e7444dfc81c95c8e013f27ac0
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <adf0398cee86643b8eacde95f17d073d022f782c
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <e137e2ba96e51902dc2878131823a96bf8e638ae
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <e97e16433eb4533083b096a3824b93a5ca3aee79
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <eb86f955488c39526534211f2610e48a5cf8ead4
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.
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