CVE-2026-99524
Received Received - Intake

Use-After-Free in Linux Kernel sched_ext

Vulnerability report for CVE-2026-99524, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the Linux kernel's sched_ext component. It occurs when a local reenq node is left on an inactive CPU's run queue. The issue arises because balance callbacks are refused once a CPU starts shutting down, but dispatch operations may still request reenqs during this window. These reenqs may never execute, leaving the node on the queue. When the scheduler is freed, it attempts to free the node again, causing a use-after-free scenario.

Impact Analysis

This vulnerability could lead to system instability or crashes due to memory corruption. It may cause kernel panics or unexpected behavior in systems using the sched_ext scheduler. Systems with frequent CPU hotplugging are more exposed to this issue.

Mitigation Strategies

Update the Linux kernel to the latest stable version that includes the fix for CVE-2026-99524. Monitor kernel logs for warnings related to scheduler or CPU hotplug issues.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-99524. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...