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

Published Nov 19, 2026
·
Updated

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

schedext: 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 queuebalancecallback() 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 dispatchone() requests one the same way.

A reenq requested from elsewhere for a cpu that is already offline goes through irqworkqueueon(), 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, scxschedfreercuwork() 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 irqwork, which balance push doesn't affect. The grace period after the cpu goes inactive waits for any requester that saw it active, so that irqwork is queued while the cpu is online.

Affected Software

3 affected componentsFixes available
linux/kernel>=7.1.0<7.3.2
7.3.2
debian/linux<7.3.3-1
7.3.3-1
debian/linux
6.1.176-16.1.192-26.12.107-16.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.3-1
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Event History

Nov 19, 2026
CVE Published
via MITRE·02:44 PM
Data Sourced
via MITRE·02:44 PM
Description
Data Sourced
via OSV·02:44 PM
DescriptionAffected Software
Data Sourced
via NVD·03:18 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203