CVE-2026-23311 (GCVE-0-2026-23311)

Vulnerability from cvelistv5 – Published: 2026-03-25 10:27 – Updated: 2026-03-25 10:27
VLAI?
Title
perf/core: Fix invalid wait context in ctx_sched_in()
Summary
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
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6 , < c67ab059953e3b66cb17ddd6524c23f9e1f6526d (git)
Affected: f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6 , < 825f218ca70ef394c2b8546b313711d867b24584 (git)
Affected: f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6 , < 486ff5ad49bc50315bcaf6d45f04a33ef0a45ced (git)
Create a notification for this product.
    Linux Linux Affected: 6.15
Unaffected: 0 , < 6.15 (semver)
Unaffected: 6.18.17 , ≤ 6.18.* (semver)
Unaffected: 6.19.7 , ≤ 6.19.* (semver)
Unaffected: 7.0-rc2 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/events/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c67ab059953e3b66cb17ddd6524c23f9e1f6526d",
              "status": "affected",
              "version": "f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6",
              "versionType": "git"
            },
            {
              "lessThan": "825f218ca70ef394c2b8546b313711d867b24584",
              "status": "affected",
              "version": "f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6",
              "versionType": "git"
            },
            {
              "lessThan": "486ff5ad49bc50315bcaf6d45f04a33ef0a45ced",
              "status": "affected",
              "version": "f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/events/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.15"
            },
            {
              "lessThan": "6.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.17",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0-rc2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.17",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.7",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0-rc2",
                  "versionStartIncluding": "6.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf/core: Fix invalid wait context in ctx_sched_in()\n\nLockdep found a bug in the event scheduling when a pinned event was\nfailed and wakes up the threads in the ring buffer like below.\n\nIt seems it should not grab a wait-queue lock under perf-context lock.\nLet\u0027s do it with irq_work.\n\n  [   39.913691] =============================\n  [   39.914157] [ BUG: Invalid wait context ]\n  [   39.914623] 6.15.0-next-20250530-next-2025053 #1 Not tainted\n  [   39.915271] -----------------------------\n  [   39.915731] repro/837 is trying to lock:\n  [   39.916191] ffff88801acfabd8 (\u0026event-\u003ewaitq){....}-{3:3}, at: __wake_up+0x26/0x60\n  [   39.917182] other info that might help us debug this:\n  [   39.917761] context-{5:5}\n  [   39.918079] 4 locks held by repro/837:\n  [   39.918530]  #0: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: __perf_event_task_sched_in+0xd1/0xbc0\n  [   39.919612]  #1: ffff88806ca3c6f8 (\u0026cpuctx_lock){....}-{2:2}, at: __perf_event_task_sched_in+0x1a7/0xbc0\n  [   39.920748]  #2: ffff88800d91fc18 (\u0026ctx-\u003elock){....}-{2:2}, at: __perf_event_task_sched_in+0x1f9/0xbc0\n  [   39.921819]  #3: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: perf_event_wakeup+0x6c/0x470"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-03-25T10:27:06.915Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c67ab059953e3b66cb17ddd6524c23f9e1f6526d"
        },
        {
          "url": "https://git.kernel.org/stable/c/825f218ca70ef394c2b8546b313711d867b24584"
        },
        {
          "url": "https://git.kernel.org/stable/c/486ff5ad49bc50315bcaf6d45f04a33ef0a45ced"
        }
      ],
      "title": "perf/core: Fix invalid wait context in ctx_sched_in()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23311",
    "datePublished": "2026-03-25T10:27:06.915Z",
    "dateReserved": "2026-01-13T15:37:45.994Z",
    "dateUpdated": "2026-03-25T10:27:06.915Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-23311\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-03-25T11:16:27.327\",\"lastModified\":\"2026-03-25T15:41:33.977\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nperf/core: Fix invalid wait context in ctx_sched_in()\\n\\nLockdep found a bug in the event scheduling when a pinned event was\\nfailed and wakes up the threads in the ring buffer like below.\\n\\nIt seems it should not grab a wait-queue lock under perf-context lock.\\nLet\u0027s do it with irq_work.\\n\\n  [   39.913691] =============================\\n  [   39.914157] [ BUG: Invalid wait context ]\\n  [   39.914623] 6.15.0-next-20250530-next-2025053 #1 Not tainted\\n  [   39.915271] -----------------------------\\n  [   39.915731] repro/837 is trying to lock:\\n  [   39.916191] ffff88801acfabd8 (\u0026event-\u003ewaitq){....}-{3:3}, at: __wake_up+0x26/0x60\\n  [   39.917182] other info that might help us debug this:\\n  [   39.917761] context-{5:5}\\n  [   39.918079] 4 locks held by repro/837:\\n  [   39.918530]  #0: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: __perf_event_task_sched_in+0xd1/0xbc0\\n  [   39.919612]  #1: ffff88806ca3c6f8 (\u0026cpuctx_lock){....}-{2:2}, at: __perf_event_task_sched_in+0x1a7/0xbc0\\n  [   39.920748]  #2: ffff88800d91fc18 (\u0026ctx-\u003elock){....}-{2:2}, at: __perf_event_task_sched_in+0x1f9/0xbc0\\n  [   39.921819]  #3: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: perf_event_wakeup+0x6c/0x470\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/486ff5ad49bc50315bcaf6d45f04a33ef0a45ced\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/825f218ca70ef394c2b8546b313711d867b24584\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c67ab059953e3b66cb17ddd6524c23f9e1f6526d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.