The vulnerability is caused by a race between the core scheduling pick_next_task routine and the core‑wide flip logic. When a pick_task releases the core‑wide lock, an in‑flight flip can rebind the rq_lockp() under a different core, causing the selection process to resume on split locks and modify sibling state that is no longer protected, leading to lock leaks and corruption of scheduler data structures.

All Linux kernel releases that do not contain the commit 23eda24f325a6e6d686d30ec75f2e9d6745e2015 are impacted. The issue is confined to the kernel’s core scheduling code.

The CVSS score of 7.8 indicates high severity. The EPSS probability is less than 1%, suggesting a low likelihood of exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector appears to be a race condition that would need precise timing between normal scheduling operations and an in‑flight core flip. Based on the description, it is inferred that only privileged kernel‑level code could reliably trigger this race, making exploitation difficult. Successful exploitation could cause a scheduler crash or denial of service but does not provide privilege escalation or direct data leakage.