LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23311: perf/core: Fix invalid wait context in ctx_sched_in()

In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix invalid wait context in ctx_sched_in() Lockdep found a bug in the event scheduling when a pinned event was failed and wakes up the threads in the ring buffer like below. It seems it should not grab a wait-queue lock under perf-context lock. Let's do it with irq_work. [ 39.913691] ============================= [ 39.914157] [ BUG: Invalid wait context ] [ 39.914623] 6.15.0-next-20250530-next-2025053 #1 Not tainted [ 39.915271] ----------------------------- [ 39.915731] repro/837 is trying to lock: [ 39.916191] ffff88801acfabd8 (&event->waitq){....}-{3:3}, at: __wake_up+0x26/0x60 [ 39.917182] other info that might help us debug this: [ 39.917761] context-{5:5} [ 39.918079] 4 locks held by repro/837: [ 39.918530] #0: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: __perf_event_task_sched_in+0xd1/0xbc0 [ 39.919612] #1: ffff88806ca3c6f8 (&cpuctx_lock){....}-{2:2}, at: __perf_event_task_sched_in+0x1a7/0xbc0 [ 39.920748] #2: ffff88800d91fc18 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_in+0x1f9/0xbc0 [ 39.921819] #3: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: perf_event_wakeup+0x6c/0x470

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23311 is a Linux kernel perf subsystem bug involving unsafe lock ordering during event scheduling. The public record says it has been fixed, but does not describe a business impact such as data theft, privilege escalation, or service outage.

Executive priority

Treat this as a kernel maintenance item until impact details improve. It deserves tracking in patch governance, but the provided evidence does not justify emergency action absent vendor severity, exploit evidence, or business-critical exposure.

Technical view

The issue is in perf/core ctx_sched_in(). Lockdep reported an invalid wait context when a failed pinned event woke ring-buffer waiters while perf context locks were held. The fix moves wakeup handling through irq_work to avoid taking the wait-queue lock under the perf-context lock.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions identified by the CVE data. The bundle lists Linux kernel versions including 6.15, 6.18.17, 6.19.7, and 7.0, but distribution backports and exact package status must be verified with vendor advisories.

Exploitation context

No active exploitation is cited, and CISA KEV status is false. The available source describes a lockdep-detected kernel locking bug, not a public exploit path or confirmed attacker impact.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability statement, or operational impact is provided. Analysis should focus on upstream commit review, distro backport mapping, and whether local perf access policies materially affect exposure.

Mitigation direction

  • Check Linux distribution advisories for CVE-2026-23311 package status.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize systems exposing perf functionality to untrusted users or workloads.
  • Track kernel backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and container hosts.
  • Compare installed kernels against vendor advisories for CVE-2026-23311.
  • Confirm whether the referenced stable commits are present in deployed kernels.
  • Document any systems awaiting a vendor-fixed kernel package.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23311 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf4b07fd62d4d11d57a15cb4ae01b3833282eb8f6, f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6, f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6unaffected
LinuxLinux6.15, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.