Critical Race Condition in Linux Kernel Kprobe Initialization

linux Updated 04 Nov 2025

Summary

28/10/2025
N/A
No i
Unrated
Not published

DEBIAN-CVE-2025-40042: In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race condition in kprobe initialization causing NULL pointer dereference There is a critical race condition in kprobe initialization that c... Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is the core component of many operating systems, providing essential services for hardware management and system resource allocation. It is widely used in various distributions, including Debian. The kernel's kprobe functionality allows developers to dynamically insert probes into running kernel code, enabling debugging and performance monitoring. However, a critical vulnerability has been identified in the kprobe initialization process, which can lead to system instability and crashes.

Vulnerability Detail

In the Linux kernel, a race condition in the kprobe initialization can lead to a NULL pointer dereference, resulting in a kernel crash. This vulnerability arises when the kprobe activation and perf_events initialization occur simultaneously across different CPU cores. If a probe is triggered before the perf_events structure is fully initialized, it can cause the system to crash, leading to potential data loss and service disruption. The vulnerability is identified as CVE-2025-40042.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds available for this vulnerability. The best course of action is to apply the necessary updates as soon as they are available.

Conclusion

The CVE-2025-40042 vulnerability in the Linux kernel poses a significant risk due to a race condition in kprobe initialization. Users are strongly advised to update their systems to the patched version of the kernel to prevent potential crashes and data loss. Monitoring tools like Vulert can assist in identifying vulnerabilities in your software.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2025-40042 is a critical vulnerability in the Linux kernel related to a race condition in kprobe initialization, which can lead to a NULL pointer dereference and kernel crash.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.

The vulnerability can lead to system crashes, data loss, and service disruption, affecting the stability and reliability of systems running the vulnerable kernel.

Yes, a patch has been released for the Linux kernel to address CVE-2025-40042. Users should update their kernel to the latest version to apply the fix.

While there are no specific workarounds, it is crucial to prioritize updating your kernel as soon as possible to mitigate the risks associated with this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback