CVE-2025-21965: Linux kernel · sched_ext: Validate prev_cpu in scx_bpf_select_cpu_dfl()
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 29 Oct 2026, 23:34 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel by validating the prev_cpu parameter in scx_bpf_select_cpu_dfl(). Users should apply the official kernel updates that include this validation.
Description
A vulnerability in the Linux kernel's sched_ext component allows a BPF scheduler to cause a kernel crash by providing an invalid CPU identifier as prev_cpu to the function scx_bpf_select_cpu_dfl(). This issue has been resolved by adding validation of the prev_cpu parameter to prevent invalid CPU values.
References
- nvd.nist.gov/vuln/detail/CVE-2025-21965 (opens in a new tab)
- git.kernel.org/stable/c/515680e76c536dd4aa8e2b5d674b0d441baddf5b (opens in a new tab)
- git.kernel.org/stable/c/752b56bb76e2471197d25d6948d85753043b10da (opens in a new tab)
- git.kernel.org/stable/c/9360dfe4cbd62ff1eb8217b815964931523b75b3 (opens in a new tab)