Kernel crash via incorrect allocation error return
Published Apr 3, 2025 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernel versions allows local users to crash the system through Bluetooth 6LoWPAN processing. The chan_alloc_skb_cb() callback returns NULL after a socket-buffer allocation failure even though its callers expect error pointers, causing later error handling to dereference the null return. Low-privileged local access and a reachable Bluetooth 6LoWPAN path are required; successful exploitation interrupts availability by crashing the kernel.
Summary
What happened
NULL pointer dereference in affected Linux kernel versions allows local users to crash the system through Bluetooth 6LoWPAN processing. The chan_alloc_skb_cb() callback returns NULL after a socket-buffer allocation failure even though its callers expect error pointers, causing later error handling to dereference the null return. Low-privileged local access and a reachable Bluetooth 6LoWPAN path are required; successful exploitation interrupts availability by crashing the kernel.
The record
- CVE
- CVE-2025-22007
- Published
- Apr 3, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2025CVE 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.17
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <1bd68db7beb426ab5a45d81516ed9611284affc8
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <72d061ee630d0dbb45c2920d8d19b3861c413e54
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <761b7c36addd22c7e6ceb05caaadc3b062d99faa
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <76304cba8cba12bb10d89d016c28403a2dd89a29
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <788ae2ae4cf484e248b5bc29211c7ac6510e3e92
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <a78692ec0d1e17a96b09f2349a028878f5b305e4
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <b3d607e36fef4bd05fb938a8a868ff70e9fedbe2
- Affected versionversion=6b8d4a6a03144c5996f98db7f8256267b0d72a3a <ecd06ad0823a90b4420c377ef8917e44e23ee841
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