{"id":"CVE-2026-99524","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:\n\nsched_ext: Fix use-after-free of a local reenq node left on an inactive cpu\n\nA local DSQ reenq is queued on the rq through a per-sched node and run from\ndeferred work. When the reenq is requested from dispatch, the work is a\nbalance callback queued once dispatch is done. A cpu going down installs\nbalance push early in its teardown, and queue_balance_callback() refuses new\ncallbacks from then on. ops.dispatch() keeps running on that cpu until the\nrq goes offline after an RCU grace period, so a reenq it requests in that\nwindow may never run. The IMMED handling in dispatch_one() requests one the\nsame way.\n\nA reenq requested from elsewhere for a cpu that is already offline goes\nthrough irq_work_queue_on(), which warns, and its work doesn't run until the\ncpu comes back.\n\nEither way the node stays on the rq's list. When the scheduler is freed,\nscx_sched_free_rcu_work() warns and frees the pcpu with the node still\nlinked, and the list is walked again once the cpu comes back.\n\nAn inactive cpu's local DSQ holds only tasks that are bound to it or are\nbeing moved off, so the reenq is pointless. Ignore reenqs of an inactive\ncpu's local DSQ.\n\nThe test is lockless. The hotplug thread of a cpu going down runs on that\ncpu, and it marks the cpu inactive before it installs balance push. A\ndispatch on the cpu runs to completion before that thread can run there, so\na dispatch that saw the cpu active has queued its callback by then. Requests\nfrom outside dispatch run from the wakeup path or through irq_work, which\nbalance push doesn't affect. The grace period after the cpu goes inactive\nwaits for any requester that saw it active, so that irq_work is queued while\nthe cpu is online.","modified":"2026-11-19T17:01:26.932964398Z","published":"2026-11-19T14:44:36.404Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99524.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/0b5282963734a51b6dad978ccfe0fa22c4d4fb17"},{"type":"WEB","url":"https://git.kernel.org/stable/c/43e1ef14a47257ebf7e3bb3ab9a6df9c6f817c5f"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99524.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99524"}],"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"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"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"}}],"schema_version":"1.9.2"}