Kernel crash via unchecked skb_clone failure
Published Jul 19, 2026 · Updated Jul 19, 2026
A NULL pointer dereference in the Linux Kernel Bluetooth 6LoWPAN subsystem allows attackers to crash systems during multicast transmission. The send_mcast_pkt() function passes skb_clone() output to send_pkt() without checking for allocation failure, leaving send_pkt() to dereference a NULL skb pointer. The fault requires an active Bluetooth 6LoWPAN multicast path and a failed GFP_ATOMIC clone allocation; the documented consequence is a kernel crash.
Summary
What happened
A NULL pointer dereference in the Linux Kernel Bluetooth 6LoWPAN subsystem allows attackers to crash systems during multicast transmission. The send_mcast_pkt() function passes skb_clone() output to send_pkt() without checking for allocation failure, leaving send_pkt() to dereference a NULL skb pointer. The fault requires an active Bluetooth 6LoWPAN multicast path and a failed GFP_ATOMIC clone allocation; the documented consequence is a kernel crash.
The record
- CVE
- CVE-2026-63991
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=18722c247023035b9e2e2a08a887adec2a9a6e49 <2061d080a013c0ec0a56162cd501fb36d2befc26
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <3c40d381ce04f9575a5d8b542898183c3b4b38dc
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <3d5d81d294ba09487c86bc4ba33dc4a4bec5d215
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <9903a04becf059e44cccf625e23689b7d4378384
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <9afcb5ea080af13aab37930da627db43bd277665
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <b06203ac5f12929d79146bb9f063c2af1d679e63
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <d630c4b25f36e0e68461561e4c70957ec37fdedd
- Affected versionversion=18722c247023035b9e2e2a08a887adec2a9a6e49 <e673889a35a5e4c586d0fae67d8755ca4367d3e2
- Affected versionversion=3.14
What conditions does exploitation require?
What is affected?
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