Kernel crash via kprobe initialization race
Published Oct 28, 2025 · Updated Oct 28, 2025
Race condition in the Linux tracing subsystem allows local users to crash the kernel by activating a profiling kprobe. During perf_kprobe_init, perf_trace_event_init enables the kprobe before other CPUs are guaranteed to observe the perf_events pointer, so kprobe_perf_func dereferences NULL. Local low-privileged access that can configure and trigger profiling kprobes is required; successful triggering causes a kernel crash and host service interruption.
Summary
What happened
Race condition in the Linux tracing subsystem allows local users to crash the kernel by activating a profiling kprobe. During perf_kprobe_init, perf_trace_event_init enables the kprobe before other CPUs are guaranteed to observe the perf_events pointer, so kprobe_perf_func dereferences NULL. Local low-privileged access that can configure and trigger profiling kprobes is required; successful triggering causes a kernel crash and host service interruption.
The record
- CVE
- CVE-2025-40042
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 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=2.6.33
- Affected versionversion=50d780560785b068c358675c5f0bf6c83b5c373e <0fa388ab2c290ef1115ff88ae88e881d0fb2db02
- Affected versionversion=50d780560785b068c358675c5f0bf6c83b5c373e <1a301228c0a8aedc3154fb1a274456f487416b96
- Affected versionversion=50d780560785b068c358675c5f0bf6c83b5c373e <5ebea6561649d30ec7a18fea23d7f76738dae916
- Affected versionversion=50d780560785b068c358675c5f0bf6c83b5c373e <95dd33361061f808d1f68616d69ada639e737cfa
- Affected versionversion=50d780560785b068c358675c5f0bf6c83b5c373e <9cf9aa7b0acfde7545c1a1d912576e9bab28dc6f
- Affected versionversion=50d780560785b068c358675c5f0bf6c83b5c373e <a6e89ada1ff6b70df73f579071ffa6ade8ae7f98
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