Kernel crash via unchecked null L2CAP socket
Published May 26, 2026 · Updated May 26, 2026
Null pointer dereference in Linux Kernel Bluetooth L2CAP allows local users to crash the kernel during channel state changes. The l2cap_sock_state_change_cb() callback reads chan->data into sk and writes sk->sk_state without first checking whether sk is NULL. Reaching the faulty callback requires local low-privilege access; published materials do not disclose the exact trigger, and only availability is affected.
Summary
What happened
Null pointer dereference in Linux Kernel Bluetooth L2CAP allows local users to crash the kernel during channel state changes. The l2cap_sock_state_change_cb() callback reads chan->data into sk and writes sk->sk_state without first checking whether sk is NULL. Reaching the faulty callback requires local low-privilege access; published materials do not disclose the exact trigger, and only availability is affected.
The record
- CVE
- CVE-2026-45834
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 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.1
- Affected versionversion=89bc500e41fc5b48e0573e6b0d927fc97b8951dc <1810e42ff6716f320c7269d5850eca48b07b7427
- Affected versionversion=89bc500e41fc5b48e0573e6b0d927fc97b8951dc <2ff1a41a912de8517b4482e946dd951b7d80edbf
- Affected versionversion=89bc500e41fc5b48e0573e6b0d927fc97b8951dc <5105f3e6b2df619c635b5f6a49fac131a36c7952
- Affected versionversion=89bc500e41fc5b48e0573e6b0d927fc97b8951dc <a2dcf1a61d056aef15b63c6eae9441344d624389
- Affected versionversion=89bc500e41fc5b48e0573e6b0d927fc97b8951dc <c88c185ae0a1067823661b220aeea613df2c127b
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