Local kernel panic via unchecked L2CAP socket pointer
Published Apr 22, 2026 · Updated Apr 22, 2026
NULL pointer dereference in Linux Kernel Bluetooth L2CAP allows local users to trigger a kernel panic through L2CAP connection handling. The l2cap_sock_ready_cb callback uses its sk pointer without first testing it for NULL, allowing timeout work to enter socket locking with an invalid pointer. Reachability requires low-privileged local access and Bluetooth L2CAP activity; successful triggering crashes the kernel without reported data exposure or modification.
Summary
What happened
NULL pointer dereference in Linux Kernel Bluetooth L2CAP allows local users to trigger a kernel panic through L2CAP connection handling. The l2cap_sock_ready_cb callback uses its sk pointer without first testing it for NULL, allowing timeout work to enter socket locking with an invalid pointer. Reachability requires low-privileged local access and Bluetooth L2CAP activity; successful triggering crashes the kernel without reported data exposure or modification.
The record
- CVE
- CVE-2026-31510
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.6
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <03d4eafb0f3788239df63575951f6b4c97bbfda4
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <0780f9333852971ca77d110019e3a66ce5a7b100
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <1dc6db047919ecd59493cd51248b37381bbabcbb
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <3c821bc0fbeaa27910a20d0b43c6008d099792af
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <898b89c90ff9496e64b9331040778cc4e1b28c9d
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <a04a760c06bb591989db659439efdf106f0bae76
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <b6552e0503973daf6f23bd6ed9273ef131ee364f
- Affected versionversion=54a59aa2b562872781d6a8fc89f300d360941691 <d34776c7fa1f2c510f1cdd14823aba701babb4ad
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