Kernel crash via enabled kprobe removal
Published Sep 15, 2025 · Updated Sep 15, 2025
NULL pointer dereference in Linux kernel kprobes allows local users to crash affected kernels by removing an enabled probe. The kill_kprobe() path sets KPROBE_FLAG_GONE before checking kprobe_disabled(), so the check always fails and leaves the ftrace probe armed instead of calling disarm_kprobe_ftrace(). Local low-privileged access and an enabled kprobe are required; the stale probe can reach kprobe_ftrace_handler and dereference a null pointer, interrupting the host.
Summary
What happened
NULL pointer dereference in Linux kernel kprobes allows local users to crash affected kernels by removing an enabled probe. The kill_kprobe() path sets KPROBE_FLAG_GONE before checking kprobe_disabled(), so the check always fails and leaves the ftrace probe armed instead of calling disarm_kprobe_ftrace(). Local low-privileged access and an enabled kprobe are required; the stale probe can reach kprobe_ftrace_handler and dereference a null pointer, interrupting the host.
The record
- CVE
- CVE-2022-50266
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record 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=2295608b44c91df767a5c68027f9c9e52ecb28e7
- Affected versionversion=247c62ebdfae450bb76dd89cd4724df6be07df75
- Affected versionversion=3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e <0c76ef3f26d5ef2ac2c21b47e7620cff35809fbb
- Affected versionversion=3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e <c909985dd0c0f74b61e3f8f0e04bf8aa9c8b97c7
- Affected versionversion=3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e <f20a067f13106565816b4b6a6b665b2088a63824
- Affected versionversion=3995f7a60feceba6c8f762f4aff3184f90a1291d
- Affected versionversion=3c5f8d371b7fef3e3714c4a062c7f3b4aa41d122
- Affected versionversion=5.9
- Affected versionversion=9b55d84deec88c02b053a819acf08a6d471dda02
- Affected versionversion=ce7ff920092130f249b75f9fe177edb3362fefe8
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