CVE-2026-23311
Invalid Wait Context Bug in Linux Kernel perf/core Scheduling
Publication date: 2026-03-25
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux_kernel | linux_kernel | 6.15.0-next-20250530-next-2025053 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's perf subsystem, specifically in the event scheduling code within the function ctx_sched_in().
The issue involves an invalid wait context caused by locking a wait-queue lock while already holding the perf-context lock, which is not allowed. This leads to a bug detected by Lockdep, a kernel locking correctness validator.
The problem occurs when a pinned event fails and wakes up threads in the ring buffer, causing improper locking sequences that can lead to kernel warnings or instability.
The fix involves changing the locking mechanism to use irq_work instead of grabbing the wait-queue lock under the perf-context lock.
How can this vulnerability impact me? :
This vulnerability can cause kernel instability or crashes due to improper locking in the perf event scheduling code.
Such instability may lead to system hangs, degraded performance, or unexpected behavior in applications relying on the Linux kernel's performance monitoring features.
While no direct data breach or privilege escalation is described, system reliability and availability could be negatively affected.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as an invalid wait context bug detected by Lockdep in the Linux kernel's perf/core subsystem. It can be identified by examining kernel logs for specific error messages related to invalid wait contexts during event scheduling.
- Check kernel logs (e.g., using dmesg) for messages containing 'BUG: Invalid wait context' and references to perf_event functions such as __perf_event_task_sched_in or perf_event_wakeup.
- Use the command: dmesg | grep 'BUG: Invalid wait context'
- Look for stack traces in the logs that mention locks held by processes related to perf events.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved in the Linux kernel by fixing the invalid wait context in the perf/core subsystem. Immediate mitigation involves updating the Linux kernel to a version that includes this fix.
- Upgrade your Linux kernel to a version released after 2026-03-25 that contains the patch for the invalid wait context in ctx_sched_in.
- If upgrading immediately is not possible, consider disabling or limiting the use of perf events or related profiling tools until the patch can be applied.