PT-2026-90234
CVE-2026-89518
·
Published
2026-09-11
·
Updated
2026-09-24
Description by
CVSS 4.0
5.7
MediumMetricsAV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions
Linux kernel (affected versions not specified)
Description
An issue exists in the
sched ext component where certain kernel functions incorrectly assume that the current CPU is always the same as the dispatched runqueue (rq). Under core scheduling, ops.dispatch() may execute on a CPU different from the dispatched rq's. This leads to several problems:- The
scx dsq move()function may incorrectly identify if an rq lock is held, potentially causing a deadlock when acquiring the source rq lock while already holding the dispatched rq lock. - The
scx bpf sub dispatch()function may dispatch a NULL value forsub dispatch prevwhen targeting a sibling. - The functions
finish dispatch(),scx bpf dsq reenq(), andscx bpf dsq nr queued()may resolveSCX DSQ LOCALto the local CPU's DSQ instead of the dispatched rq's.
Recommendations
At the moment, there is no information about a newer version that contains a fix for this vulnerability.
Found an issue in the description? Have something to add? Feel free to write us 👾