In the Linux kernel the commit schedule callback race condition leads to the kick_sync_wait_bal_cb function executing on a CPU different from the one it originally targeted. Because the function assumes it runs on the same CPU as the request queue, it compares against snapshots in that CPU's per‑CPU memory area. When it runs on another CPU, the comparison can fail and cause a deadlock, effectively freezing scheduling and potentially making the system unresponsive. This results in a denial of service through loss of scheduler responsiveness.

Any machine running a Linux kernel that does not contain the specific patches listed in the references is vulnerable. No vendor‑specific version numbers are provided, so the issue applies broadly to unpatched Linux kernels, regardless of distribution. Administrators should confirm whether their operating system includes the commits referenced by the two Git links and determine if the package updates from their distribution reflect these changes.

The EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog. Without an explicit CVSS score, the risk must be judged from the described behavior: a race condition that can deadlock the scheduler indicates a high severity local denial of service. Based on the description, it is inferred that the attack feasibility appears to require local access or an attacker already able to execute code in kernel mode, because the flaw is triggered by scheduling activity that only the kernel initiates. The lack of widespread exploitation data suggests the threat is currently limited to environments where the specific race condition can be exercised by an attacker with local privileges.