Skip to content
Heist/ feed
Back to feed
UnratedFix available

sched_ext: Don't run ops.dequeue() with a DSQ lock held

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Don't run ops.dequeue() with a DSQ lock held ops.dequeue() is invoked with the source user DSQ's lock still held on the consume and move paths (scx_consume_dispatch_q(), move_task_between_dsqs()). A BPF scheduler which locks the source user DSQ from ops.dequeue() - e.g. by iterating it with bpf_iter_scx_dsq - self-deadlocks. ops.dequeue() can only call the "any" kfuncs and none of them can lock a builtin DSQ, so the global and bypass paths can't deadlock; however, all DSQ locks share one lockdep class, so iterating any user DSQ from ops.dequeue() on those paths trips the recursion check. Move the invocation after the DSQ unlock on all three paths. SCX_TASK_IN_CUSTODY is cleared under the lock serializing the transfer so that the callback is invoked exactly once.

Products
Kernel
Affected versions
Not specified
Fixed versions
7.2.10
CVEs
CVE-2026-98865
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 17:15 UTC · Revision 1

Source evidence

sched_ext: Don't run ops.dequeue() with a DSQ lock held

core-osv · Original source

Published 18 Oct 2026, 15:51 UTC

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Don't run ops.dequeue() with a DSQ lock held ops.dequeue() is invoked with the source user DSQ's lock still held on the consume and move paths (scx_consume_dispatch_q(), move_task_between_dsqs()). A BPF scheduler which locks the source user DSQ from ops.dequeue() - e.g. by iterating it with bpf_iter_scx_dsq - self-deadlocks. ops.dequeue() can only call the "any" kfuncs and none of them can lock a builtin DSQ, so the global and bypass paths can't deadlock; however, all DSQ locks share one lockdep class, so iterating any user DSQ from ops.dequeue() on those paths trips the recursion check. Move the invocation after the DSQ unlock on all three paths. SCX_TASK_IN_CUSTODY is cleared under the lock serializing the transfer so that the callback is invoked exactly once.

osv:CVE-2026-98865

Kernel

Fixed versions: 7.2.10

Complete source record
{
  "id": "e9438e27a84f529f952b6546d6a68e4689733c69383d8d3bc5fcc616f3166404",
  "url": "https://osv.dev/vulnerability/CVE-2026-98865",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "sched_ext: Don't run ops.dequeue() with a DSQ lock held",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: sched_ext: Don't run ops.dequeue() with a DSQ lock held ops.dequeue() is invoked with the source user DSQ's lock still held on the consume and move paths (scx_consume_dispatch_q(), move_task_between_dsqs()). A BPF scheduler which locks the source user DSQ from ops.dequeue() - e.g. by iterating it with bpf_iter_scx_dsq - self-deadlocks. ops.dequeue() can only call the \"any\" kfuncs and none of them can lock a builtin DSQ, so the global and bypass paths can't deadlock; however, all DSQ locks share one lockdep class, so iterating any user DSQ from ops.dequeue() on those paths trips the recursion check. Move the invocation after the DSQ unlock on all three paths. SCX_TASK_IN_CUSTODY is cleared under the lock serializing the transfer so that the callback is invoked exactly once.",
    "evidence": "osv:CVE-2026-98865",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "7.2.10",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-98865",
      "aliases": [
        "CVE-2026-98865"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ebf1ccff79c43f860cbd2f9d6cfab9a462d0cb2d"
                },
                {
                  "fixed": "fe499ae9da46e297f578d4346c4c8e338c3118db"
                },
                {
                  "fixed": "cb86607ada73185f321baa7f9d94a08a3a40bbf5"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98865.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "7.1.0"
                },
                {
                  "fixed": "7.2.10"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98865.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:44.526341251Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/cb86607ada73185f321baa7f9d94a08a3a40bbf5",
        "https://git.kernel.org/stable/c/fe499ae9da46e297f578d4346c4c8e338c3118db",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98865.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-98865",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98865.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-98865",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 512517,
  "published_at": "2026-10-18T15:51:26.449+00:00"
}