Kernel crash via unchecked L2CAP parent pointer
Published May 26, 2026 · Updated May 26, 2026
NULL pointer dereference in the Linux Kernel Bluetooth L2CAP subsystem allows local users to crash the kernel during connection handling. The l2cap_sock_new_connection_cb() callback reads chan->data as a parent socket and passes it to lock_sock() without first checking whether it is NULL. Reachability requires low-privileged local access to exercise the Bluetooth L2CAP connection path; successful triggering interrupts the entire host, without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in the Linux Kernel Bluetooth L2CAP subsystem allows local users to crash the kernel during connection handling. The l2cap_sock_new_connection_cb() callback reads chan->data as a parent socket and passes it to lock_sock() without first checking whether it is NULL. Reachability requires low-privileged local access to exercise the Bluetooth L2CAP connection path; successful triggering interrupts the entire host, without reported data disclosure or modification.
The record
- CVE
- CVE-2026-45835
- 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=80808e431e1ef25856457de82ce141bed6a6313a <0a120d96166301d7a95be75b52f843837dbd1219
- Affected versionversion=80808e431e1ef25856457de82ce141bed6a6313a <741e6024e31587b0c021b6616a9e428a4ea0b64a
- Affected versionversion=80808e431e1ef25856457de82ce141bed6a6313a <76083fb80f5a38ac13326b2d810f66bd07771eea
- Affected versionversion=80808e431e1ef25856457de82ce141bed6a6313a <ab77c8bc30269bee15d917059a66bea48909f5f0
- Affected versionversion=80808e431e1ef25856457de82ce141bed6a6313a <bc3bb9f40da8e53896abc2d29c6d0c6686fe4ab9
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