CVE-2026-99524

Source
https://cve.org/CVERecord?id=CVE-2026-99524
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99524.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99524
Downstream
Published
2026-11-19T14:44:36Z
Modified
2026-11-19T17:01:26Z
Summary
sched_ext: Fix use-after-free of a local reenq node left on an inactive cpu
Details

In the Linux kernel, the following vulnerability has been resolved:

sched_ext: Fix use-after-free of a local reenq node left on an inactive cpu

A local DSQ reenq is queued on the rq through a per-sched node and run from deferred work. When the reenq is requested from dispatch, the work is a balance callback queued once dispatch is done. A cpu going down installs balance push early in its teardown, and queue_balance_callback() refuses new callbacks from then on. ops.dispatch() keeps running on that cpu until the rq goes offline after an RCU grace period, so a reenq it requests in that window may never run. The IMMED handling in dispatch_one() requests one the same way.

A reenq requested from elsewhere for a cpu that is already offline goes through irq_work_queue_on(), which warns, and its work doesn't run until the cpu comes back.

Either way the node stays on the rq's list. When the scheduler is freed, scx_sched_free_rcu_work() warns and frees the pcpu with the node still linked, and the list is walked again once the cpu comes back.

An inactive cpu's local DSQ holds only tasks that are bound to it or are being moved off, so the reenq is pointless. Ignore reenqs of an inactive cpu's local DSQ.

The test is lockless. The hotplug thread of a cpu going down runs on that cpu, and it marks the cpu inactive before it installs balance push. A dispatch on the cpu runs to completion before that thread can run there, so a dispatch that saw the cpu active has queued its callback by then. Requests from outside dispatch run from the wakeup path or through irq_work, which balance push doesn't affect. The grace period after the cpu goes inactive waits for any requester that saw it active, so that irq_work is queued while the cpu is online.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99524.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
238eba8c210d02ec2908d9c9143db4edcea3bfa1
Fixed
0b5282963734a51b6dad978ccfe0fa22c4d4fb17
Fixed
43e1ef14a47257ebf7e3bb3ab9a6df9c6f817c5f

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99524.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
7.1.0
Fixed
7.3.2

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99524.json"